What this guide decides.
This page decidesWhat to record and whether a condition can be monitored, maintained, isolated or escalated for technical review.
This page does not decideA universal inspection interval, safe repair prescription, structural approval, warranty decision or permission to alter the fence.
Begin at receiving.
Record pack condition, labels, quantities, visible coating or deformation damage and shortages before installation. Keep photos and affected roll/component IDs. Do not install a questionable item merely because a later repair appears possible.
Inspect by system element.
Walk the line using run, bay, gate and interface IDs. Observe fabric tension and openings, ties and clips, tension bars and bands, rails and braces, post alignment, caps, coating, bases, bottom gaps, vegetation, drainage and adjoining structures.
Treat gates as operating equipment.
Record alignment, clearances, hinges, latches, locks, stops, rollers/guides, travel area and any control interface. Control access when operation is unreliable; do not use a fabric adjustment to mask a gate-post, foundation or control problem.
Separate local repair from system change.
A compatible tie or finish touch-up may be a product-specific maintenance action. Cutting fabric, welding coated components, changing posts, moving terminals, adding privacy screen or altering an automated gate can change the approved basis and requires the appropriate review.
Close the record, not only the defect.
For each issue, save the location, date, photos, dimensions, suspected event, approved drawing/product, disposition, responsible person, replacement component and completion evidence. Repeated damage may reveal traffic, drainage, vegetation, wind or operating causes that need a wider response.
Route observations before acting.
Use the table to expose the next decision. It is not a performance rating or a substitute for project review.
Create a traceable condition record.
Keep each output in the same revision-controlled project record.
- 01
Identify
Record run, bay, gate or interface ID and approved drawing/product reference.
- 02
Observe
Photograph and describe movement, opening, coating, component, ground and operating condition.
- 03
Triage
Monitor, maintain, isolate, supplier review, engineering review or replace.
- 04
Close
Record approved action, component, owner, date, verification and new baseline photos.
Project-input schedule.
Carry these fields into the enquiry and return unknowns as open items instead of filling them with generic values.
What a usable supplier response should return.
A useful response does more than repeat the enquiry. It identifies the exact proposed product and component basis, uses the same units and location IDs as the buyer's schedule, and distinguishes confirmed values from assumptions. Where a field depends on a survey, responsible design input, local requirement or another trade, it should remain visibly open rather than being converted into a silent typical value.
The commercial offer should also state what is included, optional and excluded; which drawing or datasheet revision controls the answer; what evidence maps to the offered configuration; and what must be approved before fabrication. This lets buyers compare like with like and prevents a quotation from accidentally closing a structural, safety, civil or compliance decision.
Questions to close before quotation or release.
- Which exact run, bay or gate is affected?
- Does the condition create an opening, sharp edge or unreliable access?
- What changed in the ground, traffic or operation?
- Which approved product and finish are present?
- Will the proposed action change the system configuration?
- What evidence closes the repair record?
Technical reference boundary.
These sources define terms and decision scope. They do not certify a XIEHENG product or approve a project.
Keep adjacent intent with its owner.
A repair enquiry needs the approved configuration and a controlled evidence package, not only a general description.
Return to the product and document schedule →