> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/openbrimfea/loads-fea/static-loads-fea/global-point-loads-fea.md). # Global Point Loads \[FEA] A Global Point Load applies a concentrated force or moment at a **coordinate location** rather than at a named node. The program finds the elements in the nominated group nearest that location and distributes the load onto them. This is the load to use when you know *where* something acts but not *which* element is there — a piece of equipment at a surveyed position, a load whose position is driven by a parameter, or a load that must stay put while the mesh around it changes. Global Point Loads **generate load**. They add nothing to stiffness or mass. {% hint style="info" %} **Compared with a Nodal Load:** a Nodal Load targets a node by name and is exact. A Global Point Load targets a position and is resolved against the model at solve time. The Global form survives re-meshing and geometry changes; the nodal form is unambiguous. Prefer the nodal form when a suitable node exists and the geometry is stable. {% endhint %} ## Point Load **Load Case:** The analysis case the load belongs to. With no case assigned it applies nowhere. **Group:** The FE Group searched for elements to receive the load. This is a **connectivity** parameter and it is the critical one on this object. *Engineering influence.* The load is distributed onto elements **within this group**. If the group does not contain anything near the specified location, the load has nowhere to go and is silently lost — the model solves, and the load simply is not there. If the group contains more than you expect, the load may land on the wrong member. Because there is no error for either case, checking reactions against the applied total is the only reliable confirmation. **Location X / Y / Z:** The coordinates the load acts at. *Engineering influence.* These place the load in space. A location that does not coincide with the structure — outside the deck, above or below it, or beyond the end of a girder — leaves the load unattached, and it disappears. When the model geometry is parametric, remember these are absolute coordinates and do **not** follow the structure unless they are driven by the same parameters. Position governs the response in the usual way: near a support the load produces shear, near midspan it produces moment. **Coordinate System:** Whether the force and moment components below are interpreted in **Global**, **Local**, or a **UCS**. **UCS:** The user coordinate system used when Coordinate System is set to UCS. Ignored otherwise. *Engineering influence.* As with nodal loads, selecting the wrong system rotates the load. A longitudinal force on a skewed or curved structure entered in global axes delivers only part of its magnitude along the intended direction and introduces a transverse component. **Fx / Fy / Fz:** Force components. **Mx / My / Mz:** Moment components. *Engineering influence.* Each acts on the corresponding degree of freedom of whatever the load is distributed to, scaling the response linearly in a linear analysis. **Sign follows the axis direction**, so a downward force in a Z-up model is a **negative** Fz. A moment applied to a region represented only by truss or solid elements has no rotational degree of freedom to act on, and will either have no effect or destabilize the model. A value of zero applies nothing in that component. ## Verification * Sum the case's reactions and compare against the total force entered. A shortfall means the load did not find anything to attach to — the usual cause is a location outside the group's elements. * Display applied loads and confirm the arrow appears at the intended position, on the intended member. * Confirm the load moved to the right place after any geometry change; absolute coordinates do not follow a parametric model. * Check the sign by inspecting the deflected shape. * For a local or UCS load, resolve the components by hand and compare against global reactions. ## Common mistakes * **A location that misses the group's elements**, so the load is silently lost. This is the characteristic failure of this object and it produces no warning at all. * **A group narrower than the region the load should reach.** * **Sign error**, applying a gravity load upward. * **Assuming the location follows a parametric model.** It does not unless driven by the same parameters. * **Using a Global Point Load where a Nodal Load would be unambiguous**, introducing avoidable uncertainty about where the load landed. * **Wrong coordinate system** on a skewed or curved structure. * **No Load Case assigned**, so the load does nothing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.openbrim.org/templates/openbrimfea/loads-fea/static-loads-fea/global-point-loads-fea.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.