Separating Fabrication and In-Service Evidence in an LNG Asset Handover

One asset can carry several different evidence histories

An LNG asset handover may contain fabrication examination reports, installation records, commissioning documents and later maintenance findings in the same folder. All can be relevant, but they answer different questions. A fabrication report describes an examination at a particular construction stage. An in-service record describes a later event under its own scope and context. Combining them into a single accepted label can obscure when the evidence was produced and what decision it supported. A useful handover preserves the lifecycle relationships while keeping those purposes distinguishable.

This article proposes a document organization workflow for facility maintenance and integrity teams. It is not a regulatory interpretation, examination procedure or operating authorization. PHMSA's LNG information distinguishes construction-related oversight from review of operation and maintenance records within its United States jurisdiction. That provides contextual support for preserving lifecycle distinctions, but its requirements should not be generalized to every facility or country. The receiving asset owner determines the applicable programme, technical authority and required handover contents. The record structure below helps those people locate and evaluate the evidence.

Define the physical boundary of the handover

Begin with the asset or system boundary and the physical items included. A package named storage system can contain components with different manufacturing histories, replacements and maintenance responsibilities. Use a boundary drawing or another agreed reference to identify what is inside the package and what is only an interface. Record functional tags separately from physical component identifiers where replacements can occur. A functional tag may remain constant while a valve, spool or other item changes, so the evidence needs to follow both the position and the physical item.

Identify the handover event itself: transfer from fabrication to construction, construction to commissioning, commissioning to operations, or one operating organization to another. Each event has a different receiving audience and set of questions. State the package's purpose and effective date. If several transfers are combined, use separate sections or indexes rather than allowing one signature to imply all responsibilities changed at once. The coordinator should capture the actual transfer decision and its scope, not infer responsibility from the presence of a completed document folder.

Preserve fabrication evidence as evidence of its original stage

For fabrication records, retain the component identity, drawing revision, examination date, applicable instruction references and reported scope. Link the report to the relevant manufacturing or assembly stage where that information is available. If a component underwent repair or replacement before installation, preserve the sequence and the related examination records. The final fabrication dossier should explain which physical item was delivered and how its reported history connects to the installed asset. A report for a removed component remains historical evidence but should not be presented as the record for its replacement.

Keep original issue status visible. A draft report, a reviewed report and an accepted dossier entry may be different document states under the project process. Record those states using the project's definitions. Do not add an accepted stamp to every source document merely because the dossier was received. Receipt, completeness review and technical acceptance are separate events. If the receiving team needs confirmation of a particular fabrication decision, link to that decision and its scope instead of treating the handover cover sheet as a substitute.

Give commissioning and transition events their own place

Commissioning and transition records can explain changes between the delivered configuration and the operating configuration. Preserve the event date, component identity, relevant work package and any resulting configuration change. This may include replacement records, revised drawings or evidence of work completed during the transition. The package should show how the installed asset relates to the fabrication dossier without assuming that every delivered item remained unchanged. Where the connection is incomplete, create a specific question with an owner and the source evidence needed to resolve it.

A baseline chosen for future comparison should be identified as such by the responsible programme owner. Do not designate the oldest available fabrication measurement as an in-service baseline simply because it is convenient. The scope, location and purpose may differ from later examinations. Preserve the original record and the explicit decision about how it may be used. If a commissioning observation remains open at transfer, state its physical boundary, current status and next decision owner. The absence of closure should remain visible even when the rest of the package is complete.

Organize in-service evidence around events and context

An in-service record should identify the physical item, examination event, reported locations, source files and relevant operating or maintenance context supplied with the work. Keep that context attributable to its source. The records coordinator should not infer service conditions from a generic process description or the facility name. A report issued during an outage may describe an examination performed earlier; preserve both dates. If the examination follows a repair or a reported condition, link the triggering event so future reviewers understand why the work was requested.

Distinguish routine campaign evidence from an investigation and from verification of a particular repair. They may use related documents but support different questions. A later report should not automatically supersede all earlier evidence for an asset, especially when it covers only a small region. Record the actual scope and limitations. Where location references changed, retain a reviewed mapping rather than relabeling historical records. This allows the receiving integrity team to decide which evidence can support a comparison and which records provide only background context.

Build a lifecycle index instead of a single status column

Use an index that links component identity, lifecycle stage, event date, document identity, revision, purpose and review status. Include a source reference and a relationship to any preceding or following event. A fabrication report can link to an installation event; an in-service report can link to a repair decision and subsequent verification. The index should make those relationships navigable without merging the documents into one undifferentiated history. Keep physical condition statements separate from document completeness and administrative transfer status.

For each handover requirement, record the evidence expected, the evidence supplied and the receiving review outcome. Missing evidence should identify a specific gap rather than a generic incomplete dossier label. For example, the unresolved issue may be the association between an installed serial number and a supplied fabrication report. That is more actionable than missing quality records. Route the question to the party with access to the source evidence, and identify which review or handover decision depends on its resolution.

Hypothetical example: a replacement spool inside a larger package

Consider a hypothetical LNG facility handover for system S-40. The dossier contains a fabrication examination report for spool SP-12, an installation drawing and a later in-service thickness report under the same functional tag. The cover sheet describes the system package as complete. During indexing, the receiving team notices that the installed spool's physical identifier differs from the identifier in the fabrication report. The coordinator opens an identity question and retains all source records. The matching functional tag is not treated as proof that the reports refer to the same physical spool.

A construction change record shows that the originally delivered spool was replaced before commissioning. The replacement is SP-12R, and its fabrication package was filed under a subcontractor's delivery reference. The coordinator links that package to the installation event and retains the original SP-12 records as superseded physical history. The later in-service report is associated with SP-12R once the identity evidence is reviewed. A commissioning observation concerning a small adjacent support remains open and is assigned to its receiving owner rather than being hidden by the overall package status.

In this hypothetical example, the handover index now distinguishes the original delivered item, the replacement installed item and the later examination event. It also states that the fabrication report and in-service report were produced for different purposes; their potential use together requires the responsible technical review. The receiving team can find the correct records without discarding the construction history. The package's completeness review is updated to reflect the resolved spool association and the still-open support observation, each with its own evidence and decision trail.

Manage open items at the transfer boundary

An open-item register should identify the issue, affected asset boundary, current evidence, response owner and decision authority. Separate a missing document from a known unresolved technical observation. They can interact, but they are not the same problem. A missing attachment may be recoverable through document retrieval, whereas a condition observation may require a technical decision beyond the records team's role. State what evidence is needed next and which receiving responsibility will apply after transfer. Avoid leaving an item assigned only to a departing project team.

Whether a package can be transferred with open items depends on the applicable project and owner arrangements. The register should support that decision rather than invent a universal release rule. If transfer is authorized with specific limitations, retain the actual decision and communicate its boundaries to the receiving team. Do not convert a conditional transfer into a fully closed status because the administrative milestone has passed. Later closure evidence should remain linked to the original issue and the transfer package it affected.

Check the handover as the recipient will use it

Test the delivered copy rather than only the internal source folder. A package can look complete inside a project system while exported links point to inaccessible locations. Confirm that the recipient can open the required reports, drawings and supporting records using the agreed formats. Identify restricted or separately controlled material through the owner's approved arrangements. Do not resolve an access problem by moving sensitive records to an uncontrolled sharing service. The practical objective is dependable access for the intended reviewers throughout the agreed record lifecycle.

Choose a small set of retrieval tasks: find the installed physical item, locate its fabrication evidence, identify a later maintenance event and find the current owner of an open observation. Ask someone unfamiliar with assembly of the dossier to perform them. Record where the package requires verbal explanation. Those gaps often reveal ambiguous aliases, missing relationship notes or unclear status definitions. Correcting them before handover is more effective than adding another broad declaration that all documents have been included.

Record-readiness checklist for the lifecycle package

Use the following checks to prepare the evidence for the receiving technical and operations teams. They concern organization and traceability, not compliance certification or permission to operate. The final required content, retention arrangements and approval path must come from the applicable programme. A checklist should make that programme easier to apply by showing where its evidence is located and where a specific unresolved question still prevents a supported conclusion.

• Define the asset boundary and the particular handover event, including the receiving team and the effective transfer date.
• Separate functional tags from physical identities and retain installation, removal and replacement events that explain changes in the asset population.
• Index fabrication, commissioning and in-service records by their original purposes, dates, scopes and applicable document revisions.
• Keep receipt, completeness review, technical acceptance and operational authorization distinct in the package's status language.
• Link any proposed comparison baseline to the responsible review decision rather than assuming that the oldest available record is suitable.
• Give open items a precise asset boundary, evidence request, response owner and receiving decision authority that remains active after transfer.
• Preserve the exact handover issue and identify subsequent amendments, including the records and decisions affected by each amendment.
• Test the recipient's copy for usable files, working references and clear paths from installed items to their relevant evidence.

Keep later amendments from rewriting earlier decisions

After transfer, newly recovered evidence may resolve a missing association or reveal that a previous assumption was wrong. Issue a traceable amendment that identifies the affected item, source record and review outcome. Preserve the original package so the earlier decision can be understood in light of the evidence available then. Notify the relevant record owners through the agreed process. Quietly replacing a file can leave the receiving team unaware that a technical review or maintenance plan may need reconsideration.

The strongest handover is not necessarily the largest dossier. It is the package that lets a reviewer distinguish construction evidence from later condition evidence, follow physical replacements and locate the authority behind each decision. Maintaining those distinctions gives future campaigns a usable history. It also makes uncertainty manageable: missing evidence becomes a defined action, while records that answer different questions remain valuable without being forced into a single acceptance claim.