Solutions / Engineering guide
Wind Project Engineering Documents: Revisions & Review Status
Several suppliers and project teams can work from different versions of the same installation information. A document register should identify which revision is issued, who reviewed it and which equipment or activity it supports before that information is used for procurement or site work.
A newer file is not automatically the approved project record.
Keep document identity, issue purpose and review status separate. The project parties must agree their responsibilities and meanings; this guide does not establish an implemented MARSTON approval system.
01 / Document register
Create an identity that survives a file-name change.
Assign a document identifier, title, originator and subject or equipment reference.
Assign a document identifier, title, originator and subject or equipment reference. Record revision, issue date and the purpose for which it was issued. Keep drawings, specifications, interface schedules and evidence reports identifiable even when their file names or formats change.
A practical register can contain document_id, revision, originator, issue_purpose, equipment_scope and current_status. These are proposed project fields. NASA’s technical-data guidance provides context for identifying and distributing information; it does not certify this register or require a NASA process for a wind project.
02 / Status meanings
Distinguish submission, review and intended use.
Agree how the project labels a draft, submitted record, reviewed issue or document released for a specified activity.
Agree how the project labels a draft, submitted record, reviewed issue or document released for a specified activity. Identify who can issue each status and what decision it represents. A supplier-issued drawing and an authority-accepted submission may have different purposes.
Record review comments and their disposition with the affected revision. A message saying received is not evidence of technical approval. Do not treat a revision sequence, a PDF stamp or a file marked final as sufficient proof that the required reviewer accepted its intended use.
03 / Issue record
Keep the recipients and supporting files together.
Use an issue record naming the documents, revisions, recipient, date and reason for transmission.
Use an issue record naming the documents, revisions, recipient, date and reason for transmission. Link comments or questions to that issue so the response can be traced. Preserve originals and clearly distinguish annotated copies from documents issued by their originator.
Agree access to confidential drawings, rights to use them and the location of the current record. Distribution permissions and review authority are separate. A publicly available marketing image should not be substituted for a controlled installation drawing simply because it is easy to share.
04 / Dependencies
Trace changes across the installation interfaces.
When a turbine, tower, controller or other component changes, identify the drawings and assessments that rely on its previous identity or dimensions.
When a turbine, tower, controller or other component changes, identify the drawings and assessments that rely on its previous identity or dimensions. A change list should name the affected interface, responsible reviewer, required updated document and closure record.
Check consistency between the equipment schedule, tower and foundation interfaces, electrical documents and acceptance scope. The interface guide provides a connection record. This page manages cross-party document use rather than defining the feasibility of an OEM product modification.
05 / Superseded issues
Avoid two conflicting versions at the point of use.
Keep earlier records identifiable with their history and disposition, while making the applicable issue clear to the authorised recipients.
Keep earlier records identifiable with their history and disposition, while making the applicable issue clear to the authorised recipients. Record which party confirms the version used for the next activity. Do not silently replace a file and lose the basis of an earlier review.
If an installer reports a discrepancy, link it to the document and revision and obtain the responsible design response. An informal correction in a photograph or chat should not become an undocumented assembly change. This guide provides no authority to alter equipment or waive a required review.
06 / Handover record
Retain the information describing the installed package.
At handover, connect the equipment identities and approved changes with the final drawing register, applicable instructions and required acceptance records.
At handover, connect the equipment identities and approved changes with the final drawing register, applicable instructions and required acceptance records. Identify outstanding documents and conditional items. A proposal register is not automatically an as-installed record.
Provide MARSTON the selected model, project document requirements and the interface records needed for its supply scope. The project’s lead party should coordinate the remaining design and local-work documents. No complete design-authority, certification or document-management service is promised by this guide.
Continue the review with Small Wind Installer & System Integrator Selection.
Continue the review with Wind Controller Protocols & Register Maps.
Continue the review with Wind Power vs Grid Extension for Remote Sites.
General background: NASA: technical-data identity, access and distribution context. These references explain industry concepts; they are separate from the applicable MARSTON product and project documents.
Prepare the information for this review.
Use the checklist to organise the project information. Mark unavailable items and retain document references.
| Review item | Information to provide | Purpose |
|---|---|---|
| Identity register | Document ID, subject, originator, revision and issue purpose | Identify each technical record. |
| Review record | Reviewer, required decision, comments and disposition | Separate receipt from acceptance. |
| Distribution log | Issue, recipients, linked files and permissions | Keep point-of-use information traceable. |
| Dependency record | Changed interface, affected documents and closure owner | Resolve cross-party consequences. |
| Installed record | Equipment identities, approved changes and outstanding items | Support future service and review. |
Engineering questions.
Is the newest file necessarily the correct issue?
Check its subject, revision, purpose and required review status. Newness alone does not establish intended use.
Does received mean approved?
No. Retain the actual review decision and agreed status meanings.
Is this the same as an OEM change request?
An OEM request concerns a proposed product modification. This register coordinates the technical documents used across the project.
Can a final PDF approve installation by itself?
The required reviewer, purpose and configuration must be established. A file label alone is insufficient.
Should superseded issues lose their history?
Retain identifiable history and disposition while making the applicable point-of-use issue clear.
What should remain at handover?
The installed equipment identity, final register, approved changes, applicable instructions and unresolved document items.
Technical enquiry
Bring your project information to the discussion.
Several suppliers and project teams can work from different versions of the same installation information. Share the available information and the equipment scope you want reviewed in a technical quotation.