Abaqus Interactions
Overview
Translate a physical interface into an explicit interaction contract. Distinguish
mechanical contact and constraints from analytical theory-to-CAE coupling, and
keep every parameter tied to an approved assumption or source.
When to use
Use when a model includes contact, tie, cohesive or surface behavior, connectors,
or kinematic/distributing coupling constraints. Use a boundary-condition review
for supports and a mesh review for interface discretization.
Inputs
- Physical interface and participating named surfaces or regions
- Separation, sliding, adhesion, friction, connector, or constraint intent
- Normal direction, initial clearance or overclosure, and activation step
- Discretization compatibility, parameter sources, and sensitivity assumptions
Outputs
Return an interface table, Abaqus object plan, activation history, parameter
provenance, conflict audit, and unresolved physical risks. State which behavior
is checked statically and which needs an approved runtime or engineering review.
Workflow
- Identify the physical interface and named regions before selecting an API.
- Distinguish tie, contact, connector, and kinematic/distributing coupling.
- Check normal direction, initial clearance, discretization, activation, and
dependency names.
- Treat friction, penalty stiffness, tolerance, and stabilization as explicit
inputs or sensitivity assumptions, never unexplained defaults.
- Define interface observations: status, relative motion, reaction, or energy
measures appropriate to the claim.
Safety gates
- Do not infer friction, stiffness, clearance, or contact behavior from an example.
- Do not use an interaction to hide a geometry, support, or convergence defect.
- Do not modify source surfaces or constraints without authorization.
- Do not call a valid interaction definition physical validation.
Example prompts
Audit a synthetic soil-structure contact plan. Separate contact, tie, and
coupling constraints; check surface names, normal direction, activation step,
friction provenance, and required interface observations.
Common failures
- Reversing master/slave or normal orientation without checking the interface.
- Activating a tie or contact before the surfaces exist or after they change.
- Treating penalty defaults as calibrated material behavior.
- Confusing analytical-to-CAE coupling with an Abaqus mechanical constraint.
Acceptance checklist
1---2name: abaqus-interaction3description: Use when defining or reviewing Abaqus contact, tie, surface interaction, coupling constraints, or connectors between named regions.4---56# Abaqus Interactions78## Overview910Translate a physical interface into an explicit interaction contract. Distinguish11mechanical contact and constraints from analytical theory-to-CAE coupling, and12keep every parameter tied to an approved assumption or source.1314## When to use1516Use when a model includes contact, tie, cohesive or surface behavior, connectors,17or kinematic/distributing coupling constraints. Use a boundary-condition review18for supports and a mesh review for interface discretization.1920## Inputs2122- Physical interface and participating named surfaces or regions23- Separation, sliding, adhesion, friction, connector, or constraint intent24- Normal direction, initial clearance or overclosure, and activation step25- Discretization compatibility, parameter sources, and sensitivity assumptions2627## Outputs2829Return an interface table, Abaqus object plan, activation history, parameter30provenance, conflict audit, and unresolved physical risks. State which behavior31is checked statically and which needs an approved runtime or engineering review.3233## Workflow34351. Identify the physical interface and named regions before selecting an API.362. Distinguish tie, contact, connector, and kinematic/distributing coupling.373. Check normal direction, initial clearance, discretization, activation, and38 dependency names.394. Treat friction, penalty stiffness, tolerance, and stabilization as explicit40 inputs or sensitivity assumptions, never unexplained defaults.415. Define interface observations: status, relative motion, reaction, or energy42 measures appropriate to the claim.4344## Safety gates4546- Do not infer friction, stiffness, clearance, or contact behavior from an example.47- Do not use an interaction to hide a geometry, support, or convergence defect.48- Do not modify source surfaces or constraints without authorization.49- Do not call a valid interaction definition physical validation.5051## Example prompts5253> Audit a synthetic soil-structure contact plan. Separate contact, tie, and54> coupling constraints; check surface names, normal direction, activation step,55> friction provenance, and required interface observations.5657## Common failures5859- Reversing master/slave or normal orientation without checking the interface.60- Activating a tie or contact before the surfaces exist or after they change.61- Treating penalty defaults as calibrated material behavior.62- Confusing analytical-to-CAE coupling with an Abaqus mechanical constraint.6364## Acceptance checklist6566- [ ] Physical interface and named regions are explicit.67- [ ] Interaction type and activation history match the intent.68- [ ] Parameters, units, signs, and sources are recorded.69- [ ] Interface observations and sensitivity risks are defined.70- [ ] Static, runtime, and engineering-review boundaries are separated.
1348109517