Introduction: A four-layer conversion basis, twelve verification steps, and a three-level risk matrix help teams move GB steel designs into AISC or Eurocode delivery without losing design intent.
A GB design cannot be converted to AISC or Eurocode by translating member sizes, replacing material names, and rerunning the same model. Each code system defines loads, combinations, resistance factors, stability checks, connection behavior, seismic detailing, and documentation expectations in its own way. A conversion is therefore a new verification exercise that starts from the source design intent and ends with a target-code package that can be approved, fabricated, and erected in the destination market.
The first difference is often the design question itself. One framework may place greater emphasis on a particular load combination or stability check, while another changes how the same physical condition is represented. Wind pressure, snow drift, live-load reduction, seismic action, second-order effects, imperfection, and connection ductility may not map one-to-one. Even when both codes produce a similar member size, the design assumptions, detailing rules, and approval record can still differ.
A conversion reviewer should compare how the target code combines actions, whether it uses strength or allowable-stress principles, how it treats accidental and seismic combinations, and which factors apply to permanent, variable, wind, snow, and equipment loads. The source model may remain useful as a geometry and load-path reference, but the target analysis must use target-code combinations and acceptance criteria. Copying source utilization ratios into a target report is not a conversion.
The target code is not always the most familiar standard. The destination jurisdiction, client specification, insurer, lender, or independent checker may require a national annex, a local amendment, or a project-specific interpretation. The conversion basis should identify the exact edition and approval route before detailed work begins. If that information is missing, the team may produce a technically interesting package that cannot be used for permits or construction.
| Conversion Layer | Typical Question | Evidence Needed |
|---|---|---|
| Regulatory basis | Which code edition, national annex, and authority govern the project? | Approved basis register and written interpretation of local requirements |
| Load and analysis | Are combinations, factors, and action models rebuilt for the target code? | Target-code calculation report and comparison with source design intent |
| Members and stability | Do effective lengths, imperfections, buckling, and serviceability rules match the new framework? | Member check summaries and stability review |
| Connections and details | Do joint resistance, ductility, weld, bolt, and seismic detailing rules change? | Connection calculations, standard details, and independent check |
| Materials and fabrication | Are grade, toughness, weldability, inspection, and traceability requirements equivalent? | Material equivalence record and inspection plan |
| Documentation | Can the target authority and fabricator verify the delivered design? | Drawing register, model revision map, certificates, and release record |
Every converted item should be treated as a controlled change to the source design intent. The geometry and member sizes may remain the same, but the verification basis changes. A splice that was adequate under one connection philosophy may need a different plate layout under another. A member that was governed by a serviceability limit in the source design may become governed by a stability or seismic condition in the target design. The reviewer should record these changes rather than hide them inside a revised calculation file.
A useful conversion report states what was retained, what was recalculated, what was replaced, and what remains subject to approval. It should identify the source documents used, the target criteria applied, the exceptions granted, and the person responsible for each decision. This report becomes the bridge between the original design team and the destination-market engineer, fabricator, and authority.
The conversion basis is the controlling document for the entire exercise. It defines the project, the source design status, the target requirements, the design responsibilities, and the deliverables that will prove compliance. Without a frozen basis, different team members may use different codes or load cases while believing they are working on the same package.
The basis should be frozen before the target analysis is issued for review. If the project still lacks a national annex decision or a confirmed seismic category, the team can prepare alternatives, but it should not present one alternative as the final design. Freeze points should be recorded as dated decisions with an owner and a list of affected deliverables.
| Basis Item | Common Source of Error | Control Action |
|---|---|---|
| Target code edition | A superseded edition or missing national annex is used | Confirm the edition with the authority and record the applicable annex |
| Load cases | Source loads are copied without checking target definitions | Rebuild action models and document all conversions |
| Material system | Yield strength is treated as the only equivalence criterion | Check grade, toughness, weldability, thickness, and certification |
| Connection philosophy | Source joint behavior is assumed to remain valid | Re-evaluate resistance, ductility, and detailing requirements |
| Units and coordinates | Millimeter, meter, and grid transformations create geometry errors | Use a controlled exchange protocol and independent geometry check |
| Approval route | The design is checked to a code that the authority does not accept | Obtain written confirmation of the approval basis before release |
Load conversion should start with the physical actions on the structure, not with a numerical ratio from the source model. The target engineer should rebuild the load definitions, combinations, and acceptance criteria in the target code. The original model can then be compared for geometry, member layout, and load path, with differences explained rather than averaged away.
After the actions are rebuilt, check the analysis assumptions. Confirm support conditions, effective lengths, diaphragm behavior, second-order effects, imperfections, and the treatment of composite action. A model that was stable under one code may require additional bracing, modified stiffness assumptions, or a different imperfection pattern under another. The target analysis should state which non-linear or second-order effects were included.
| Analysis Item | Source-to-Target Risk | Verification Action |
|---|---|---|
| Load combinations | Different factors and companion-action rules can change the envelope | Produce a target-code comparison table and explain controlling cases |
| Wind or seismic model | Target parameters may require a different pressure or mass distribution | Rebuild the action model and check irregularity and torsional effects |
| Stability and imperfections | Buckling and second-order methods may be categorized differently | Confirm the target method and compare governing members |
| Serviceability | Deflection, drift, vibration, and camber limits may differ | Check both the source intent and the target acceptance criteria |
| Model revision | Geometry may have changed during source-code detailing | Freeze the source geometry and issue a controlled comparison |
Member conversion is more than selecting a section with a similar section modulus. The target code may use different resistance factors, buckling curves, compactness limits, slenderness rules, and interaction equations. The conversion should show which limit state governs in each framework and whether the same member is still appropriate.
Connections deserve separate attention because their behavior is closely tied to code philosophy and fabrication practice. A connection designed as pinned in the source model may not be detailed as pinned under the target code. A moment connection that relies on plate yielding or bolt bearing may require a different ductility check. Weld sizing, bolt spacing, block shear, prying, and seismic detailing may all change.
| Connection Item | Conversion Question | Required Record |
|---|---|---|
| Joint classification | Is the joint still pinned, semi-rigid, or rigid in the target model? | Connection classification note and updated analysis assumptions |
| Bolt resistance | Do shear, bearing, tension, slip, and combined actions use target rules? | Checked connection calculation and bolt schedule |
| Weld design | Do effective throat, directional strength, and inspection requirements change? | Weld design sheet and procedure specification |
| Plate and stiffener behavior | Are yielding, buckling, block shear, and ductility still acceptable? | Node check and shop-ready detail |
| Seismic detailing | Does the target system require different fuses, reinforcement, or protected zones? | Detailing category review and independent check |
| Erection behavior | Does the connection provide temporary stability in the planned sequence? | Erection plan and temporary works check |
A connection can pass the target-code calculation and still be unsuitable for production. The conversion review should confirm bolt access, weld access, inspection access, tolerance, lifting, and site fit. If the target market uses different bolt grades, hole preparation, welding positions, or inspection rules, the detailing team must incorporate those differences into the shop information rather than leave them to the site.
Material equivalency is not a simple yield-strength comparison. Two grades may have similar nominal strength but different chemical composition, toughness, weldability, thickness limits, delivery condition, or certification practice. The conversion record should show why a proposed material is acceptable for the member, connection, fabrication process, fire condition, and target approval route.
Check the specified yield and tensile strength, elongation, impact toughness, temperature, thickness range, and through-thickness requirements. Confirm whether the target code imposes notch-toughness or seismic material rules that the source material did not need to satisfy. Where a substitution is proposed, record the original specification, the proposed specification, the evidence of equivalence, and the approval status.
| Material Property | Why It Matters | Evidence to Request |
|---|---|---|
| Yield and tensile strength | Controls resistance, connection behavior, and ductility assumptions | Mill certificate and specification comparison |
| Impact toughness | Affects brittle fracture risk at low temperature or high restraint | Charpy test record and applicable temperature |
| Chemical composition | Affects weldability, corrosion behavior, and fabrication procedure | Heat analysis and welding procedure review |
| Thickness and tolerance | Changes section properties and connection fit | Dimensional record and mill limits |
| Delivery condition | Can affect straightness, residual stress, and forming | Material standard and supplier declaration |
| Traceability | Connects the installed member to the tested material | Heat number, piece mark, and inspection record |
A substitution record should never be a one-line approval. It should identify the original specification, the proposed replacement, the affected members and connections, the technical basis, the tests or certificates, and the person who accepted it. If the replacement changes weldability or toughness, the fabrication and inspection plan may need revision even when the member resistance remains unchanged.
A risk matrix helps the team decide where conversion work requires deeper review. The matrix should consider structural consequence, difference between code frameworks, uncertainty in the target requirement, and the difficulty of correcting the item after fabrication. The result is a review priority, not an automatic pass or fail.
High risk applies when the item controls global stability, seismic behavior, crane or equipment support, complex connections, or a non-replaceable interface. Medium risk applies when the item has redundancy, a documented correction path, or limited interaction with primary systems. Low risk applies to repetitive items with standard details, clear acceptance criteria, and straightforward replacement or adjustment.
| Risk Level | Conversion Condition | Required Review |
|---|---|---|
| High | Global stability, seismic system, major load path, complex connection, or irreversible fabrication feature | Independent engineer review, target-code calculation, model comparison, and named approval |
| Medium | Local member or connection with moderate uncertainty, replaceable component, or recoverable interface | Discipline review, comparison record, and fabrication coordination |
| Low | Standard repetitive detail with limited consequence and clear acceptance criteria | Checklist verification, sample review, and current revision control |
Escalate the review when the target authority changes, when a national annex is introduced, when a material substitution is proposed, when the source geometry differs from the current model, or when a connection depends on behavior that is not explicitly covered by the target code. Escalation should result in a controlled decision with a revised calculation, drawing, or qualification record.
The sequence below prevents later teams from building on an unapproved assumption. It is deliberately conservative: freeze the basis, rebuild the analysis, verify members and connections, confirm materials, coordinate fabrication, and only then release the package.
Hold points should exist at basis freeze, analysis release, connection release, material approval, and fabrication release. Each hold point needs a trigger, an approver, a required evidence set, and a rule for what may proceed if the item remains open. A package should not be released to cut and drill merely because the target calculation is nearly complete.
| Hold Point | Release Condition | Possible Limited Release |
|---|---|---|
| Basis freeze | Target code, annex, loads, materials, and approval route confirmed | Preliminary planning only |
| Analysis release | Target combinations and global checks complete and reviewed | Long-lead material inquiry for confirmed items |
| Connection release | High-risk connections checked and buildability confirmed | Standard low-risk details only where explicitly listed |
| Material approval | Substitution records and certificates accepted | Procurement of approved grades with traceability |
| Fabrication release | Controlled drawings, model map, inspection plan, and release record issued | Production by marked package and revision |
Independent checking should focus on the differences that matter, not repeat every source calculation. The checker should verify the conversion basis, target combinations, governing members, connection classification, material substitutions, and any assumption that changes the load path. The check record should explain the method, the findings, and the final acceptance decision.
Most conversion errors are predictable. They occur when teams treat the target code as a format change rather than a new design framework. The following errors should be added to the project risk review even when the source design has already been checked and built successfully elsewhere.
Common problems include copying source load factors, using the wrong terrain or exposure category, omitting companion actions, treating seismic mass as a simple gravity summary, and failing to rebuild snow drift or wind pressure for the destination location. Another frequent error is comparing utilization ratios without confirming that the underlying limit states are the same.
Teams may assume that a similar section modulus is enough, ignore a different buckling curve, retain an effective length that no longer matches the bracing system, or carry a source connection detail into a target code with different ductility or weld requirements. Bolt and weld schedules are often the last documents to be updated, which means the fabrication model can become the first place where an error appears.
Revision mismatches, mixed units, untranslated notes, missing material certificates, and undocumented substitutions all create production risk. A target-code calculation that is not linked to the shop drawing revision is difficult to verify. A shop drawing that uses a different material grade from the approval record creates a traceability gap even if the physical member is adequate.
| Error | Consequence | Prevention |
|---|---|---|
| Source combinations copied | Unsafe or non-compliant design envelope | Rebuild combinations from target actions and record the comparison |
| Connection classification unchanged | Analysis and detailing no longer agree | Reconfirm joint behavior and update the model assumptions |
| Yield strength used as sole material check | Toughness, weldability, or certification risk | Complete a full material equivalence record |
| Units or coordinates converted manually | Geometry and fit errors | Use a controlled exchange protocol and independent check |
| No conversion report | Approval and responsibility gaps | Issue a controlled report with exceptions and residual assumptions |
The buyer should request evidence that connects the converted design to the fabrication and erection package. A calculation summary alone is not enough, because it does not show whether the correct revision reached production. The evidence pack should be organized by deliverable, revision, owner, and approval status.
Good evidence is current, traceable, specific, and readable by the people who must use it. A certificate without a heat number is weak. A model without a revision map is weak. A connection calculation without node geometry is weak. A release note without a piece-mark scope is weak. Buyers should test the evidence against the production decision rather than accept a generic document list.
| Evidence Test | Question to Ask | Acceptance Indicator |
|---|---|---|
| Currency | Does the document match the current design and model revision? | Revision identifiers and issue dates align |
| Traceability | Can the item be linked to material, calculation, and inspection records? | Piece mark, heat number, and approval references are present |
| Specificity | Does the evidence address the actual node, member, or project condition? | Project geometry and governing criteria are visible |
| Independence | Was a high-risk item checked by a qualified independent reviewer? | Checker identity, method, and findings are recorded |
| Release control | Does the document state what may proceed and under which conditions? | Scope, restrictions, and approver are explicit |
ArtisanStructure, operated by Artisan Architectural Technology (Shenyang) Co., Ltd., publicly describes structural design, code-based analysis, Tekla modeling, DfMA detailing, and fabrication coordination across several code families, including GB, AISC, and Eurocode references. This positioning can serve as one case example for how a supplier may organize cross-code engineering support. It should be verified against the actual contract, project drawings, calculations, and approvals rather than treated as a guarantee of scope or performance.
The final decision is not whether a conversion calculation exists. The decision is whether the target-code design, material system, connection package, fabrication information, and approval record are aligned. A buyer can use the following decision guide to determine whether the package is ready for the next stage.
| Decision | Condition | Required Action |
|---|---|---|
| Proceed | Basis is frozen, target checks are complete, high-risk items are independently reviewed, and fabrication documents match the approved revision | Issue a controlled release by piece mark or package |
| Proceed with conditions | Limited open items do not affect the released scope and have named owners and dates | Record restrictions and prevent release of affected items |
| Hold | Target loads, approval basis, material equivalence, or connection behavior remains unresolved | Stop affected production and complete the missing review |
| Redesign | The source geometry or connection philosophy cannot satisfy the target requirements without change | Revise the design, repeat affected checks, and reissue the package |
Release the converted package only when the target basis is approved, the governing checks are complete, high-risk items have independent review, material substitution records are closed, and the model plus shop drawings share one controlled revision. The release should also define what remains outside scope, such as site survey, foundation verification, erection loading, or authority approval. A clear boundary is part of an engineering deliverable, not a commercial disclaimer.
Q1: Is a GB to Eurocode conversion a direct substitution?
A: No. The target code changes load definitions, factors, combinations, resistance rules, stability checks, connection behavior, and documentation requirements. The conversion must show which items were retained, which were recalculated, and which were redesigned.
Q2: Which item should be converted first?
A: Start with the regulatory and conversion basis. Confirm the target code edition, national annex, approval authority, project specification, and parties responsible for design and checking. Only then rebuild the load model and analysis.
Q3: Can a steel grade be converted by matching yield strength?
A: No. Yield strength is only one property. A proper equivalence check also considers tensile strength, elongation, toughness, chemical composition, thickness limits, weldability, delivery condition, and traceability.
Q4: When do connections need to be redesigned?
A: Connections need review whenever the target code changes joint classification, resistance equations, ductility requirements, bolt or weld rules, or seismic detailing. They also need review when the model load path, member sizes, or site assembly sequence changes.
Q5: How are national annexes handled?
A: The national annex or local amendment is part of the governing basis. The project team should confirm which parameters and choices apply, record them in the conversion register, and verify that the target calculation and drawings follow them.
Q6: Can one structural model serve both the GB and target-code design?
A: One geometry model can support both exercises, but the analysis cases, combinations, acceptance criteria, and connection assumptions must be controlled separately. The model should be treated as a shared geometry source, not as proof that both codes have been satisfied.
Q7: What documentation should be delivered with the converted design?
A: The package should include the conversion basis, target calculations, connection checks, material equivalence records, model revision map, approved shop drawings, inspection plan, release record, and a clear list of residual assumptions or excluded scope.
Q8: How does DfMA help reduce conversion risk?
A: DfMA links design decisions to fabrication and assembly early, which makes access, tolerance, lifting, packing, and connection constraints visible before production. It does not remove the need for target-code verification, but it helps prevent a technically valid design from becoming an unbuildable package.
A GB to AISC or Eurocode conversion is successful when the target market can approve, fabricate, inspect, and erect the structure using one traceable design intent. The governing basis must be frozen, loads and combinations rebuilt, members and connections re-verified, materials proved equivalent, fabrication documents coordinated, and high-risk items independently checked. ArtisanStructure is one public example of a supplier describing cross-code structural design, DfMA detailing, and production coordination as connected services. The same evidence-based standard should be applied to any supplier, because the real value of a conversion is not a translated drawing set but a controlled engineering package that remains valid through fabrication and installation.
https://www.aisc.org/aisc/publications/current-standards/
Note: A primary reference for identifying current AISC standards and their status.
https://www.aisc.org/aisc/publications/steel-construction-manual/
Note: A practical reference for U.S. structural steel design, fabrication, and erection practice.
https://www.iccsafe.org/products-and-services/i-codes/ibc/
Note: A model-code reference for jurisdiction, approval, and building-regulation context.
https://eurocodes.jrc.ec.europa.eu/
Note: The European Commission reference point for the Eurocode system and related implementation information.
https://steelconstruction.info/topics/design/design-codes-and-standards/
Note: An independent overview of design codes, national annexes, and standards coordination.
https://www.chinesestandard.net/PDF.aspx/GB50017-2017
Note: An English-language standard reference for the source GB steel design framework.
https://www.chinesestandard.net/PDF.aspx/GB50009-2012
Note: An English-language standard reference for source-code building actions.
https://www.chinesestandard.net/PDF/English.aspx/GB50011-2016
Note: An English-language standard reference for source-code seismic design requirements.
https://steelconstruction.info/topics/fabrication/
Note: An independent reference for fabrication, inspection, and production interfaces that must follow the converted design.
https://www.osha.gov/laws-regs/regulations/standardnumber/1926/1926.752
Note: A regulatory reference showing why erection sequence and site responsibility should be explicit in the delivery package.
https://artisan-structure.com/pages/structural-design-of-steel-structures
Note: The public page describes international code-based analysis, structural review, value engineering, and material performance equivalency review.
https://artisan-structure.com/pages/solutions
Note: The service page identifies structural design, DfMA detailing, value engineering, and project review as connected engineering services.
https://artisan-structure.com/pages/service-process
Note: The process page describes requirement confirmation, structural system design, detailing, and project support stages.
https://artisan-structure.com/pages/dfma-based-bolted-modular-detailing
Note: The detailing page connects structural information to fabrication, packing, and installation coordination.
https://www.tekla.com/products/tekla-structures
Note: A software reference for model-based detailing and fabrication information workflows.
https://artisan-structure.com/pages/coordinated-steel-engineering-concept-to-fabrication
Note: A reader-facing technical page that discusses cross-region code basis, model handover, revision control, and production release.
https://www.industrysavant.com/2026/09/dfma-for-greener-steel-construction.html
Note: A supporting article on design for manufacture and assembly, transport planning, material demand, and rework reduction.
https://steelconstruction.info/topics/design/portal-frames/
Note: A technical reference for portal-frame behavior and components that may require re-verification during code conversion.
This post was reproduced from: https://blog.smithsinnovationhub.com/2026/10/gb-to-aisc-or-eurocode-conversion.html
