Hello!

Did you know that logged in users can see a lot more content?

Support articles

8. ProNest 2019 Cheat Sheet

Tekla EPM to ProNest Integration Cheat Sheet Steps to use ProNest as an external combining Software including taking from Stock in EPM. In order. (For those already familiar with the process) From the combining run (with ProNest as the Nesting Software), export the parts for nesting. Save the combining run. Import the parts list to ProNest and nest the job. Crop all nests. Save remnants and skeletons. (Understand the ramifications if you omit this step - don't go back and do it later). Export CNC. (This is optional at this point - you can do it here or later, or even both). Generate the
Requires Tekla Maintenance
by Tekla Support US
0

7. ProNest 2019 Cut List Import

Import and Process Production for a ProNest Cut List Cutting a nest produces new inventory - remnants. Follow these steps to get this remnant information back from ProNest and entered into Tekla EPM's inventory. Send nests out to CNC Sending a nest to CNC, from the ProNest standpoint, fabricates the piece. This step must be taken before importing a cut list in to EPM. The process of sending nests to CNC populates the ProNest database with information about the nests and the remnants created. Afterward, EPM can add those remnants to the EPM inventory. If the ProNest to EPM Nest Summary report
Requires Tekla Maintenance
by Tekla Support US
0

6. ProNest 2019 External Nesting

Taking a Nesting run to ProNest and back Use this process to take advantage of ProNest's Nesting capabilities within a Tekla EPM job. Open a job in Combining, Estimating, Production Control or Purchasing. Choose "Combine" from the menu. Click "Nest" or "Mult & Nest" at the bottom to start a new combining run. From the "Combining Run Filters" screen, click "Optimizations" (bottom left) to select the nesting software to use. If PNL/SNL Nesting File format is used, the inventory available to this Combining Run can be restricted using the INV Filter (next to Optimization button). Choose
Requires Tekla Maintenance
by Tekla Support US
0

5. ProNest 2019 Inventory Import

Import Inventory from ProNest On occasion, when first beginning to use the integration from EPM to ProNest, or when some nesting has been performed in ProNest outside of the integration, ProNest may contain inventory and remnants that did not originate through the integration. Follow these steps to bring that inventory in to EPM and make it available to the integration for use in nesting. Export Inventory From ProNest From ProNest, open the Plate Inventory. Select plates to import to EPM (plates not selected will not be included). Choose File→Print. You'll see a Print Preview-type screen.
Requires Tekla Maintenance
by Tekla Support US
0

4. ProNest 2019 Inventory Sync

Keep ProNest and Tekla EPM inventory in sync by regularly exporting the EPM Inventory to ProNest. From Inventory, choose Export, then Sync with ProNest. The export command creates an inventory export file, then triggers ProNest's Data Sync to process that file. When Data Sync has processed the file, EPM checks the ProNest database for the new pieces and links each new piece in ProNest Inventory to the appropriate piece in the EPM inventory. When this process is complete, ProNest should have all the inventory that EPM has. Inventory that had previously been in ProNest (but not linked to EPM
Requires Tekla Maintenance
by Tekla Support US
0

3. ProNest 2019 Initial Setup

ProNest Integration Setup These tasks must be performed before using the ProNest Integration. Verify that ProNest and DataSync are working If you're not sure that they're working, refer to the Pre-Setup requirements task list. Enable ProNest Integration On the Tekla EPM Maintenance Menu, select Integration Settings, then ProNest Check Enable ProNest for Plate Nesting. This adds the option to send the inventory to ProNest, and adds ProNest as a choice of nesting software for a combining run. Nesting Request File Format A nesting request can be sent either using the Work Order service, or
Requires Tekla Maintenance
by Tekla Support US
0

2. ProNest 2019 Integration Pre-Setup requirements

Tekla EPM to ProNest Integration Pre-Setup Requirements Before trying to connect ProNest and EPM, a few basic pieces should be in place. This document details the steps to verify that each piece is installed and working correctly. From ProNest Check versions of ProNest and DataSync against the Integration Requirements. Contact your ProNest representative for necessary updates. This integration requires that the Networked database from ProNest be installed, and also requires some specific licenses from ProNest. DataSyncCmd must be installed properly on the FabSuite server. DataSyncCmd.exe must
Requires Tekla Maintenance
by Tekla Support US
0

ProNest 2019 Integration (Start Here)

ProNest 2019 Integration Overview ProNest 2019 Integration Pre-Setup requirements ProNest 2019 Initial Setup ProNest 2019 Inventory Sync ProNest 2019 Inventory Import ProNest 2019 External Nesting ProNest 2019 Cut List Import ProNest 2019 Cheat Sheet
Requires Tekla Maintenance
by Tekla Support US
0
  • ProNest
  • Hypertherm
  • Integration
  • Plate Nesting

1. ProNest 2019 Integration Overview

This Tekla EPM to ProNest 2019 Integration is designed to reduce the effort in making EPM and ProNest work together. Specifically, we hope to reduce or eliminate the manual double-entry of inventory and parts. Requirements Tekla EPM 2019 or newer ProNest 2019 ProNest DataSync 2019 What to do Before starting, Make sure that ProNest and Data Sync are communicating. Then set up EPM and ProNest to work together. Send ProNest the current EPM inventory. (This can be done automatically). Or (optionally), import inventory and/or remnants from ProNest into EPM. Send a combining run to ProNest for
Requires Tekla Maintenance
by Tekla Support US
0

Installing a Second Database

Installation of a second database can facilitate training and testing in an environment that will minimize impact on you production database.  There is more than one way to do this.  The server installation of the program can be done on any machine, so if the purpose of the second database if for an individual’s use then it is likely that the simplest solution is to run the installer on that individual’s machine, provided it is not the server, as a server install.  This would install the database on that machine and the connection for it would be localhost with the default port remaining as
Requires Tekla Maintenance
by Tekla Support US
0
  • Second Database
  • Test Database

Emergency Uses

Emergency uses are not easily replaced, but they can be reset by support. These are available initially as three per machine.  The licensing is improved to reduce the overall maintenance required.  It is important to understand that as part of the backup to these improvements the ability to use emergency uses still exists to prevent any hardship due to unexpected loss of access to the online system. It is important to note that there are multiple situations that may require emergency uses in order to log on in the absence of a connection to the internet, access to the license server or an
Requires Tekla Maintenance
by Tekla Support US
0
  • Unable to Login
  • Emergency Use
  • Licenses

2019i Beta Release

2019i Beta  Estimating IFC Import Enhancements Estimating IFC import will now update existing items based on GUID matching when an updated file is imported into the same estimate, previously the incoming records would always get added Estimating IFC import now presents a field mapping screen to give you the option of mapping IFC property sets to fields in the estimate.  The possibility of a UDA in Tekla Structures populated with the labor code or estimate extra, that is then included in the IFC export, and mapped to the correct field in EPM is a prime example. In Maintenance > Estimating
Requires Tekla Maintenance
by Tekla Support US
0
  • Enhancements Estimating Production Control Accessory

Automated Events - Overdue Drawings

Automated Events is a handy tool for Project Managers to notify clients of overdue approval drawings or RFI status updates.  This document is intended to help you with setting up an automated event for overdue drawings, though you may use this same tool to send other types of notices, so be sure to take the time to review the long list of reports available for use within the system. To begin, verify that the Outgoing Email Settings have been entered.  With the window for ‘Automated Events’ open, click the Automated Events drop down, and then click to select ‘Outgoing Email Settings’ to open
Requires Tekla Maintenance
by Tekla Support US
0
  • Automated Events
  • Overdue Drawings

Error Installing Crystal Reports Viewer: 1603

Problem: The user will get this message at the beginning of the installation process of the program.  It began with version 5.2.4r06 and later:  “Error Installing Crystal Reports Viewer: 1603” Solution: Error message 1603 is a new error message when installing the 5.2.4 release.  You should be able to complete the installation process.  Then log in and try opening the Default Directory and changing the Crystal Report Viewer Version from Crystal Reports 2013 to Crystal Reports XI.  Close the program to reset it to the new viewer, then reopen and try again. If that does not fix the problem then
Requires Tekla Maintenance
by Tekla Support US
0
  • Crystal Reports

Customize Grid

Customize Grid I think that the power of customizing the module ‘Select’ windows is the most overlooked aspect of the program.  We are so busy with learning to work or working in the program that we completely skip taking a closer look at how customizing a grid may help us out.  As a trainer, I often get questions, like: "How do I get a fabricated weight total report for the AISC?" or "How do I use this program to get a win/loss report in Estimating?".  To answer these questions, I show off the 'Customize Grid' feature while I am working with them, but I thought that it would be helpful here
Requires Tekla Maintenance
by Tekla Support US
0
  • Customize Grid

Reporting in Estimating

I wanted to take this opportunity to discuss Estimating reports.  When I train new Tekla EPM users, viewing and using reports is the best way to gain program trust. Those using Estimating in Tekla EPM for the first time may feel lost and, frankly, a bit fearful.  Using a new system, is not comfortable, ever.  I was one of those who developed my own trusted estimating spreadsheet, back from the time of programs like Lotus 1-2-3 and Symphony, then Excel as soon as it arrived in the market.  I do understand what it takes to make the switch and gain confidence with using this program.  I can tell
Requires Tekla Maintenance
by Tekla Support US
0
  • Estimating Reports
  • Project Summary Report

Error Message 1062

There are two MySQL error 1062 Messages.  The one I am in reference to here reads:   MySQL error 1062 – “Duplicate entry "12064" for key 1 INSERT INTO UserSessions (UserID, IPAddress, User, ConnectionID, TimeLogOn)VALUES (10, 'localhost', name of user@computer’s IPAddress, 8, date & time stamp")” The solution reads: There are two different MySQL error 1062 messages.  If the error message makes reference to “UserTables” or “UserSessions” then you will need to do the following.  If the user cannot log into the program you have to manually repair the issue.  This action is done on the server
Requires Tekla Maintenance
by Tekla Support US
1
  • Error Message 1062

Tekla EPM Plugin

The Tekla EPM Plugin (formerly FabSuite TME) allows for seamless communication between Tekla EPM and Tekla Structures. The Tekla EPM Plugin integrates with Tekla Structures allowing you to: Export the Tekla Structures model into a compressed EPM XML file. This single file contains the Drawings, Revisions, Bill of Materials, User-Defined Attributes, CNC Files, and Drawing Files. Import an EPM XML file into Tekla Structures to update the model with the current status information and colorize the model based on those statuses. Installation The Tekla EPM Plugin supports and is installed with
Requires Tekla Maintenance
by Tekla Support US
0
  • Tekla TME

System Requirements

Minimum Client Specifications: Operating System: Windows 7 Memory: 2 GB Disk Space: 2 GB Display Resolution: 1024×768 Recommended Client Specifications: Operating System: Windows 7 / 8.1 / 10 Memory: 4GB RAM Disk Space: 4GB Minimum Server Specifications: Operating System: Windows Server 2008 Memory: 8 GB Server Disk Space: 10 GB Recommended Server Specifications: Operating System: Windows Server 2008 / 2012 / 2016 Memory: 12GB RAM Server Disk Space: 100GB reserved for Tekla EPM (software and data), solid state drive (SSD) Standard drives are acceptable, but SSD’s truly make a difference in
Requires Tekla Maintenance
by Tekla Support US
0
  • System Requirements

Using Production Control Jobs with Trimble Connect

Using Production Control Jobs with Trimble Connect Note: It is recommended to start your Production Control job with the EPM Plugin XML export from Tekla Structures. The XML includes GUIDs, unique identifiers that will match those in the IFC model. The EPM plugin (formerly FabSuite TME) will be available for download from the Tekla Warehouse. Production Control can share many statuses with Connect, as seen in the "Status Sharing Setup" section above. For example, whether production has been started or completed: Or status in various stations: Or shipping status: With the Multiple Actions
Requires Tekla Maintenance
by Tekla Support US
0
  • Trimble Connect
  • Production Control Model View
  • Linking jobs to Trimble Connect

Pages