On occasion, when first beginning to use the integration from Tekla EPM to SigmaNest, or when some nesting has been performed in SigmaNest outside of the integration, SigmaNest 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 SigmaNest
From SigmaNest, open the Sheet List.
Select plates to import to EPM (plates not selected will not be included if you export Selected Plates).
Check the box beside Tekla EPM
Keep SigmaNest and Tekla EPM inventory in sync by regularly exporting the EPM Inventory to SigmaNest.
From Inventory, choose Export, then Export to SigmaNest.
The program queries SigmaNest for all linked inventory, then sends updates (quantity changes and newly received material) to SigmaNest through SimTrans.
Errors are not returned to EPM from SimTrans, please monitor your SimTrans program to find errors.
DON'T SEE "EXPORT TO SIGMANEST" IN THE INVENTORY EXIT MENU?Make sure SigmaNest is enabled.
PROGRAM GOT AN ERROR WHEN EXPORTING INVENTORY TO SIGMANEST?Check to make sure
Download these two reports
Place these reports in your SNData folder, under Reports/English-USA or Reports90/English-USA
To add the Tekla EPM Layout Detail report to Nesting, open the Nesting tab, then click Report, then Print. Note that you may need to open a workspace for the Report button to be active.
Click Setup, then Add.
Choose "Tekla EPM Layout Detail.fr3" in the File list, then click Open and Okay.
Close the task report, then Re-open it, click Print again. "Tekla EPM Layout Detail" should now be in the list of Reports:
To automatically generate this report when you
The Tekla EPM to SigmaNest Integration eliminates manual double entry of inventory and parts.
In order to accomplish this, we have added tools to perform these tasks:
Inventory Export sends or updates inventory from Tekla EPM to SigmaNest. This integration is intended to have Tekla EPM as the primary data source, keeping SigmaNest up to date via SimTrans.
HTML Inventory Import allows SigmaNest to send inventory (particularly remnants) to Tekla EPM that were created outside the integration.
Nesting Export and Results Import allows SigmaNest to nest a combining run from Tekla EPM. Parts (but
It's possible to run a job in Steel Projects and use inventory from Tekla EPM without actually creating the project in Tekla EPM.
To enable this workflow, in Tekla EPM under the Maintenance dropdown select Integration Settings → Steel Projects. Make sure "Allow Nests without a Tekla EPM Job:" is checked.
This is an example of a possible workflow. Your use of SP-PLM will probably differ.
For this example we'll start by importing DSTV files generated by our detailing software in to SP-PLM:
Then from the Project Manager tab we'll select the Project that we just imported, then the Drawing tab.
Saving the Cut List
Sending PLM a cut list and receiving feedback is the most common workflow for this integration. This can be done as a standalone workflow, or as an additional step to the nesting request workflow.
Open the Production Control Job, select "Review" then "Cut Lists" from the Production Control menu.
At the bottom of the window, click "New Cut List".
Filter your selection if needed, click "Make Report", then "Save Cut List"
Enter a description and due date for your cut list. Make sure to check "Share Cut List" so SP-PLM can import it.
Now, the new cut list will show up on the
A work order is a request for nesting and/or multing that includes the CNC files to be cut, as well as the available and orderable stock on which to nest or mult. To have Steel Projects perform the Nest or Mult, export your Combining run to XML and import it in to Steel Projects.
To create this work order from Tekla EPM, open Combining from the Combining, Estimating, Production Control Requisition or Purchase Order Modules. Then Choose "Combine" from the Module drop-down menu. Here it is shown from Production Control.
Choose "Mult" for bars or "Nest" for plates (PLM can do both) then click "
From the "Fabrication Job data" tab click "Import"
Next to "Link" enter a work order name and click "New"
From the Type dropdown select FabSuite - Nest request import Select the directory where Tekla EPM exports the nest request
Click Save, then Quit.
Click Import again
For Link enter a name for the cutlist import then click New
For Type select FabSuite - Plugin - Cut list, then click Options
Open your Tekla EPM Remote Monitor and click Settings. You will need the IP Address and Socket Port for the next step.
Back in PLM in the Options window, enter "tcp://" then the IP address
To Enable Steel Projects choose Maintenance->Integration Settings->Steel Projects.
Check "Enable Steel Projects". If you want Steel Projects to be able to reserve material to a job that doesn't exist in Tekla EPM, check that box.
If you have Remote Link or EPM GO:
Create an external user
From the File dropdown select Administration
Select the External Users tab
Name your user. Be sure to record the password.
Give your user permission to log in, and required Tekla EPM permissions.
Make sure Remote Server is running.
Note: The remaining setup is on the Steel Projects side. They
Steel Projects PLM Integration
Tekla EPM can send inventory or a combination run as a work order to Steel Projects. This allows the CNC Files and available inventory to be bundled for Steel Projects and reduces manual double entry.
1. Setup in Tekla EPM
2. Setup in Steel Projects PLM
3. Sending a Work Order>
4. Saving a Cut List in Tekla EPM and Importing the Cut List in to SP-PLM
5. The "No Tekla EPM Job" Workflow
• Tekla EPM 2019 or newer.
• Steel Projects PLM 1.8.x or newer
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).
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
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).
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).
You'll see a Print Preview-type screen.
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
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
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.
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
This Tekla EPM to ProNest 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.
Tekla EPM 2019 or newer
ProNest 2019 or newer
ProNest DataSync 2019 or newer
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
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