STRUCTURE CUBE / WORK GUIDE / V3.0.4

← Written tasks

Load partial factors: settings, adoption and review

Change with a clear basis: distinguish local new-load defaults, project adoption and historical records.

Follow → Verify → Repeat independently
01

Find Load factors and check the seven parameters against the project basis.

CHECKOpen Home > Pipe load tables > Load factors, or Configure load factors on a service reference page. There is no active load-adjustment K. Inputs must be finite positive numbers with up to three decimal places. Software references are not universal project recommendations.

View the actual interface and notes
STRUCTURE CUBE / V3.0.4REFERENCE CAPTURE
V3.0.4 Light reference · Water Pipe Load page with the Configure load factors entry. This is not the seven-factor settings page.
V3.0.4 Light reference · Water Pipe Load page with the Configure load factors entry. This is not the seven-factor settings page.
02

Save the local defaults and verify the save confirmation.

CHECKA modified status is not a saved value: use Save settings and check confirmation. Restored defaults still require Save; Discard changes returns to the last saved values. Free and enterprise editions keep separate local defaults.

03

Keep an existing load and create a genuinely new load for comparison.

CHECKNew defaults apply only to subsequent new loads. Existing loads retain adopted records when edited, copied, restored or reopened. Copying is not a new-default test. Keep the old item while comparing rather than deleting unconfirmed data.

04

Distinguish characteristic values, design values and manual design inputs.

CHECKService partial factors convert corresponding characteristic components into design actions. Manual input is a design input: 100 N adopts 100 N, without extra K or default pipe factors. Check N, N/m, direction and design/characteristic basis before comparing.

05

Preserve historical adopted records before deciding to recreate an action.

CHECKRemoving K does not divide or recalculate older actions. Historical adopted loads retain actual design and characteristic values; missing derivations must not be invented. Back up before changing size or spacing. Confirming historical self-weight rebuilding affects all project member self-weight; cancellation leaves the related change uncommitted.

06

Save, recalculate and match the report to adopted project records.

CHECKReports read saved project adoption records for loads and self-weight, not current exporting-computer defaults. Match IDs, sizes, positions, spacing, basis and factors. Missing historical records produce an adopted-value notice; changing defaults must not overwrite the old basis.

REPEAT / CHECK / EXPLAIN

Repeat independently, without the prompts.

For self-review on this page only; not saved after leaving and not engineering approval or training certification.

Scope, cautions and knowledge references

Do not reduce factors merely to pass a check or divide historical actions by K. Member self-weight retains the permanent factor adopted when the project was created; moving computers does not replace it with new defaults.

Identify the entry, saved state, adoption scope and report basis. Real engineering safety still requires professional review of actual conditions.

Reviewed Xiaoan entries: load-factors-start · load-factors-save · load-factors-basis · load-factors-manual · load-factors-selfweight · load-factors-history · load-factors-report · load-factors-screenshot

← Back to written tasks

XiaoanV3.0.4 GUIDANCE

MEIGONA AI Technical Assistant

A CLEARER NEXT STEP

Hello, I’m Xiaoan.
Where can I help?

Find a usage guide, or put together a clear description of an issue.

V3.0.4 usage guidance is available. AI availability is checked on opening; uncertain issues can go to human support.

Enter to send · Shift+Enter for a new line