Compare Wind Blade NDE Before and After a Repair

A wind blade repair record becomes difficult to use when the before and after examinations describe different locations or use incompatible reference points. Begin by identifying the blade, the repair event and the physical area each examination covers. The purpose of a comparison is to explain what evidence relates to the repaired feature, not to create an attractive pair of images that appear similar. Keep the original observations and their context available. If the later examination cannot be matched confidently to the earlier area, state that limitation and ask the responsible reviewer what additional evidence is needed.

The free NDT reporting workspace can organize entered observations, references and comparison tables into a PDF. It does not align native instrument datasets, reconstruct a blade model or determine whether a repair restores structural capacity. This guide provides a practical documentation approach for preserving the repair footprint, location convention and examination context across events. The inspection method, repair design, acceptance criteria and return-to-service decision remain those established by the responsible project process. Use the downloadable worksheet as a comparison aid, then replace every fictional example with the actual references for the blade being reported.

Record the blade identity from the approved asset and inspection records. A turbine position or temporary yard label may help people find it, but that label alone may not remain stable through removal, repair and reinstallation. Explain how the blade identifier relates to the turbine, work order and repair event. Preserve leading zeros and suffixes where they distinguish assets. If the original record uses a different identifier from the current maintenance system, document the relationship using supported evidence rather than silently renaming the blade in the new report.

Check whether the earlier and later examinations concern the same physical blade and repair area. A fleet campaign can produce many similar-looking files, particularly when the same repair pattern is repeated across several units. Match each source record deliberately. If a photograph or data file has an ambiguous filename, consult its associated work record rather than treating the filename as definitive. The comparison worksheet should identify the source report and event for both sides. This makes a later review possible even when the reader has no access to the technician's original folder arrangement or recollection of the visit.

Use the project's approved location convention to describe the repair area. Relevant references may include distance from a defined datum, blade side, edge relationship and an orientation note. State what the datum means and how distances or positions are measured. A number without a reference origin can look precise while remaining impossible to relocate. If the blade changes position between events, explain which references remain fixed to the blade and which depend on how it is being viewed. Avoid relying on left and right without a defined viewing direction.

Document any change to the location convention before comparing results. An earlier record may use a spanwise reference while a later repair drawing adds a local grid. Create a supported cross-reference between them and identify where the mapping is uncertain. Do not force an exact match where the evidence only supports a broader area. The report can distinguish confirmed matches, approximate associations and unresolved locations in plain language. These are documentation categories, not statistical confidence estimates. The technical reviewer determines whether the available location evidence is sufficient for the intended repair assessment.

Keep the physical repair footprint distinct from the area examined. A repair may cover a defined zone, while an examination includes surrounding material or only an accessible portion of that zone. The report should identify both boundaries so that a reader can understand what the results support. Reference the approved repair drawing or work record and the examination coverage evidence. If the repair boundary changed after additional damage was found, retain the relationship between the original proposal and the completed repair. Do not describe the proposed footprint as if it were the final work performed.

Sandia's blade reliability and composite materials research describes blade-specific inspection specimens and research into defects and damage. That context supports careful identification of the feature and material being examined; it does not provide acceptance criteria for this report. Record the actual repair and inspection requirements from the authorized project documents. A generic phrase such as blade inspected can conceal whether the bond region, repaired surface or another feature was within scope. Use the level of detail needed to make the comparison meaningful.

Identify the method and procedure reference for each event, including the revision and relevant setup information required by the project. A before examination and an after examination may use different techniques, access arrangements or reporting conventions. Those differences do not automatically invalidate all comparison, but they must be understood before drawing a conclusion. Preserve the original context rather than rewriting both records into identical wording. Where a reviewer determines that a particular observation can be compared, record the basis for that decision and any limits on what the comparison demonstrates.

Avoid interpreting a change in displayed appearance as a change in the blade without checking acquisition and presentation differences. Image scaling, view selection and processing can affect what a reader sees. The reporting tool can reference source files and describe observations, but it does not verify acquisition equivalence or process native inspection data. Keep the original files in the approved evidence system and identify the relevant views or records precisely. If a comparison relies on a specialist analysis outside the report, cite that analysis rather than presenting an unsupported visual impression as a quantified repair result.

Define the event represented by each record: initial condition, preparation, an intermediate repair stage or examination after the completed repair. The same area may look different because material has been removed, added or finished between stages. A useful report makes those transitions explicit. Do not place an intermediate observation in a final-result column simply because it is the clearest photograph available. Associate each observation with the stage and date it describes. Where a stage was not examined or its evidence is unavailable, record that fact instead of filling the gap with an image from another event.

The final baseline should identify the evidence selected to support future comparison after the repair has reached the defined completion state. That selection is a project decision and should be traceable to the relevant review. A final baseline is not a guarantee that the blade has no defects, nor does it replace the repair acceptance process. It is a dated reference for the condition and examination scope actually documented. Preserve any limitations that will matter to a future inspector, including areas not covered or differences that prevent direct comparison with the earlier record.

Create one row per feature or area that the reviewer needs to follow. Include the blade and repair identifiers, location reference, earlier event, later event, source evidence, comparability note and unresolved question. A row should make the relationship between the two events understandable without implying that their values can always be subtracted or ranked. If the earlier evidence only identifies a broad zone, say so. If the later record covers an expanded repair boundary, identify the added area separately rather than implying that the entire later scope has a matching historical observation.

NIST's research on linking design, manufacturing and inspection information describes the challenges of connecting information across lifecycle stages. The worksheet here is a simple manual response to that kind of information problem, not a claim that the reporting tool implements a digital twin or a fully integrated data chain. Use stable references and explicit relationships. The value comes from making the evidence retrievable and its meaning clear, even when the original repair, inspection and asset systems remain separate.

If an area could not be examined using the planned arrangement, describe the affected boundary and the reason in the inspection record according to the project requirements. Avoid a broad completed statement that hides an access limitation. A later examination may reach an area that the earlier one did not, or may lose access because the repair changed the surface or configuration. These situations should appear in the comparison table. They do not justify assigning a historical result to the unexamined area or concluding that no change occurred simply because there is no matching earlier observation.

Use a clear unresolved-action entry when additional review is needed. Identify the question, the responsible person and the evidence required to answer it. The free procedure generator can help organize the inputs for a proposed examination approach, but the generated draft does not authorize a changed technique or supply repair acceptance. Similarly, the equipment tracker can organize the instruments used for the events without establishing that their outputs are directly comparable. Keep those supporting tool functions connected to the task while preserving the technical decisions that must be made through the project's approved process.

Consider a fictional blade repair identified as R-07. The initial examination describes an area using a spanwise datum and a side designation. During preparation, the approved repair footprint expands beyond the original marked area. The after-repair examination covers the completed footprint and a documented surrounding zone. The author creates separate comparison rows for the area with supported earlier evidence and for the added repair area. The latter row does not invent a before result. It identifies the preparation-stage evidence and the reason the original examination cannot provide a direct baseline for that added area.

In the same fictional case, one earlier image lacks a reliable orientation reference. The author retains it as supporting context but does not use it as proof of an exact location match. The reviewer receives the uncertainty and decides what further evidence is needed. The final report identifies the confirmed comparison and its limits. No numerical defect threshold or repair acceptance rule is supplied by this example. Its purpose is to show how a useful record can preserve an imperfect history honestly, allowing the responsible reviewer to distinguish supported conclusions from questions that still require attention.

In the reporting workspace, enter the blade and repair identity, inspection dates, scope, procedure references and the paired evidence table. Use observations to explain meaningful differences between events and the conclusion to summarize only the supported assessment. Reference drawings, photographs and native files through the approved document system. The current tool does not package every external evidence file automatically. Keep company and client logos separate from technical approval statements. A branded report should still explain who made the relevant repair and examination decisions and where their supporting records can be found.

Download a draft PDF and check the location labels, stage descriptions and source references at normal reading size. Long identifiers should not become ambiguous after wrapping, and table headings should make it clear which event each column describes. Read the report without referring to your working notes to see whether its comparison can stand on its own. Correct any misleading shorthand, then save the intended draft and create a new proof. A previously downloaded PDF remains unchanged. Issue the saved record only after the required project review has been completed and its evidence is retained.

At closeout, retain the selected baseline report, its supporting evidence index and the location convention used to describe the repair. Explain any unresolved historical mismatch that a future team will encounter. A useful handover allows another inspector to find the same feature and understand why some observations are comparable while others are not. Avoid presenting a neat trend chart if the underlying records do not support a consistent series. The quality of a future comparison depends on the clarity of today's references, not simply on the number of files stored in an archive.

For later inspections, begin with the preserved baseline and confirm the blade's identity and configuration again. Add a new event rather than overwriting the earlier condition. If a report error is discovered after issue, create a draft revision through the reporting workflow and communicate the correction through the project's process. Use the equipment and procedure tools to organize current supporting information, while keeping the historical baseline intact. The downloadable worksheet is designed to make these relationships visible; it remains a reporting aid and does not replace the blade owner's engineering, maintenance or return-to-service decisions.

Include a small retrieval exercise in the handover review: ask an authorized colleague to locate the final repair drawing, identify the matching examination event and explain the datum from the report alone. If the colleague needs an undocumented folder shortcut or verbal explanation, improve the reference before closing the package. Check that access permissions support the intended future use and that a temporary download link is not the only way to retrieve a key file. This exercise tests the practical usefulness of the baseline without repeating the inspection. It also reveals naming or orientation gaps while the team still has the context needed to resolve them accurately.