What KISS Files Contain
KISS files are formatted ASCII text files containing structural member data in a standardized field layout. A typical KISS file includes: piece marks, section sizes, material grades, member lengths, quantities, drawing references, coating specifications, and fabrication sequence information. The format has evolved through several versions; confirm which version your fabrication management system accepts before requesting KISS output.
Generating KISS from Tekla Structures
Tekla Structures can generate KISS files through its reports and exports module. The output quality depends on how the model was built — piece marks must be assigned, material grades must be entered on every member, and the model must be free of duplicate marks and undefined sections. A model built with KISS output in mind from the start (proper material grade entry, consistent naming conventions) produces clean KISS files; a model cleaned up for KISS output at the end often requires significant rework.
Systems That Use KISS Input
KISS files are consumed by fabrication management and ERP systems including FabSuite, StruMIS, and some versions of Stratus. Shop management systems use KISS data to populate production schedules, material purchase orders, and shipping manifests without manual re-entry from the BOM. Ask your system vendor which KISS version is supported and what field-mapping configuration is required.
KISS File Versions and Compatibility
The KISS format has evolved through several major versions since its introduction by the American Institute of Steel Construction and the National Steel Construction Conference in the 1980s. KISS Version 2 is the most widely supported; KISS Version 3 adds support for connection data, coating information, and extended piece attributes. Before requesting KISS output from a detailer, confirm with your FabSuite, StruMIS, or other ERP vendor which KISS version is accepted and whether any custom field mappings are required. A KISS file generated in the wrong version — or with fields in the wrong sequence — will either import with errors or fail entirely. Testing with a small batch of 10–15 members before committing to production-scale import is essential for any new shop-detailer KISS integration.
KISS vs. Other Data Exchange Options
KISS is one of several available data exchange formats between detailing software and fabrication management systems. Understanding the alternatives helps fabricators choose the right format for their workflow.
- KISS — ASCII text, widely supported, field-based; good for shops already using KISS-compatible ERP
- SDS/2 direct native output — if the detailer uses SDS/2, some fabrication systems accept native SDS/2 data directly without format conversion
- Tekla EPM integration — for shops using Trimble's own EPM production management platform, Tekla Structures provides deep native integration beyond what KISS offers
- CSV/XLSX export — most ERP systems can import a well-structured CSV with manual column mapping; lower friction for small shops with non-standard systems
- Custom API integration — for shops with development resources, Tekla's Open API allows custom data pipelines with real-time sync rather than batch file transfers
What the KISS File Cannot Replace
KISS files are production data, not engineering documents. They transfer member identification, geometry, and material data — but they do not replace shop drawings, CNC files, or erection drawings. A shop cannot fabricate from KISS data alone; the KISS file populates the ERP system's production schedule, material list, and work order system, while the shop drawings remain the fabrication instructions for the shop floor. Some shops use KISS data to auto-populate their work order system and attach the associated shop drawing PDF as a linked document — this combination gives production managers visibility into schedule status while giving the shop floor the drawing detail they need.
Setting Up Your Detailer for KISS Output
Getting clean KISS output from a detailer requires a one-time setup investment. Provide your detailer with: the KISS version accepted by your ERP system, a sample KISS import file showing the field structure your system expects, any custom field mappings required (e.g., your system uses a non-standard field for coating zone), and a test procedure for verifying the import before production-scale use. Document this setup in writing so subsequent projects with the same detailer can use the same configuration without re-setup. Firms like Tectonix that regularly produce KISS output maintain shop-specific configuration templates that eliminate the setup cost on repeat engagements.
KISS Revisions and Change Management
When design changes or addenda revise member sizes, quantities, or attributes after the initial KISS file is issued, a revised KISS file must be produced and imported into the ERP system. The revised file should clearly identify which piece marks are new, which are revised, and which are unchanged — some KISS implementations support delta files that contain only the changed records. If the ERP system does not support delta imports and requires a full re-import, work with your system administrator to manage the replacement carefully: re-importing a full KISS file against an already-populated production schedule can overwrite production status on members that are partially or fully fabricated. Most experienced shops lock completed members in the ERP system before importing KISS revisions to prevent production status from being reset.