V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryAs-Built Configuration
Records · The complete guide

As-Built Configuration

In short

As-Built Configuration is a time-specific snapshot of a physical manufactured product that identifies its actual installed components and revisions, including the effects of substitutions, removals, replacements and applicable authorised deviations.

4,152 words · ~19 min read
As-Built Configuration illustration showing an open pump assembly, its installed components and a separate removed component set
A configuration snapshot distinguishes installed components from those removed or replaced.
On this page
  1. 01What an as-built configuration records
  2. 02As-designed, as-planned, as-built and as-maintained
  3. 03Keep legal scope separate from configuration practice
  4. 04Capture, reconcile, review and preserve the snapshot
  5. 05Model installed content, authority and supporting evidence
  6. 06Worked case: an authorised bracket substitution
  7. 07Worked case: reconstructing a device after rework
  8. 08Reconcile systems without confusing records with reality
  9. 09Worked case: recovering a late installation record
  10. 10Failure modes that make a plausible snapshot misleading
  11. 11Test the model before relying on it
On this page · 11 sections
  1. 1What an as-built configuration records
  2. 2As-designed, as-planned, as-built and as-maintained
  3. 3Keep legal scope separate from configuration practice
  4. 4Capture, reconcile, review and preserve the snapshot
  5. 5Model installed content, authority and supporting evidence
  6. 6Worked case: an authorised bracket substitution
  7. 7Worked case: reconstructing a device after rework
  8. 8Reconcile systems without confusing records with reality
  9. 9Worked case: recovering a late installation record
  10. 10Failure modes that make a plausible snapshot misleading
  11. 11Test the model before relying on it
AI · Explain it for MY operation

How does As-Built Configuration apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01What an as-built configuration records

As-Built Configuration is a time-specific snapshot of a physical manufactured product that identifies its actual installed components and revisions, including the effects of substitutions, removals, replacements and applicable authorised deviations.

A useful snapshot has a clear coordinate: an identified physical unit or explicitly bounded group, a defined cut-off time and a stated level of component detail. That detail might stop at replaceable assemblies or extend to individual components. For a group, the boundary should make clear which units share the recorded configuration and which exceptions are recorded separately. Without these coordinates, a component list can look precise while leaving its physical applicability uncertain.

The factual question is what is installed, not whether it is acceptable. An accurate snapshot can describe an unresolved discrepancy or an unacceptable condition. Recording a substituted part does not establish its suitability; an authorised person's disposition remains a separate decision. Keeping those questions separate prevents the record from silently replacing observed content with expected content.

Within configuration management, the snapshot provides the actual-content counterpart to a configuration specification. Product traceability connects that content to supporting identities and events; production context tagging helps explain how evidence is associated with the right manufacturing context. Execution records and serial genealogy remain supporting references, rather than histories to reproduce inside the snapshot. The snapshot identifies installed content at its cut-off, not every operation performed or every upstream relationship. Computer-system configuration settings are outside this physical-product scope.

02As-designed, as-planned, as-built and as-maintained

These states answer different manufacturing questions. Select the record by whether you need intended definition, build intent, actual installed content or subsequent service changes—not simply by which record has the latest revision.

Record or stateQuestion answeredScope and time basisTypical contentsWhy it cannot replace the snapshot.
As-designedWhat is the intended product definition?Product definition at a controlled design revision.Drawings, specifications, component definitions and permitted options.Describes intent, not what was installed in a particular unit.
As-plannedWhat configuration is intended for this build?Selected configuration for a manufacturing order or unit before execution.Selected components, revisions and applicable build options.Execution may differ through authorised substitutions or rework.
As-builtWhat physically constituted this product at the cut-off?Identified unit or defined group at a stated manufacturing milestone.Actual installed identities, revisions and applicable deviation references.This is the snapshot; its validity is bounded by its identified product and cut-off.
As-maintainedWhat configuration exists following service changes?Individual product during its subsequent service life.Retained content, service replacements and modification status.Later service state does not establish the earlier manufacturing state.
Execution historyWhat happened during manufacture?Activities and decisions across the manufacturing sequence.Execution and review records.A chronological history is not itself a resolved installed-content view.
Serial genealogyWhich identified items are related?Relationships among components, assemblies and finished units.Parent–child identity links.Relationships alone may not distinguish currently installed from previously associated parts.

A bill of materials can supply the comparison baseline, but it does not establish which component identities were actually installed. Likewise, consult the device history record for manufacturing execution context and serial genealogy relationships for identity connections. Use those records alongside the snapshot rather than treating them as interchangeable views.

03Keep legal scope separate from configuration practice

For US medical devices subject to Part 820, FDA’s QMSR is revised 21 CFR Part 820, effective since 2 February 2026, incorporating ISO 13485:2016 by reference. Consult FDA’s current QMSR explanation and the final rule for applicability. Neither establishes the snapshot fields proposed here. The QMSR and ISO 13485 comparison helps frame that distinction.

Before mapping an as-built record to an obligation, answer these questions:

  • Jurisdiction: Which market and legal framework apply to the product?
  • Product type: Is the item a medical device, pharmaceutical, supplement, food or chemical?
  • Regulated activity: Does the assessment concern manufacturing, installation, servicing or another activity?
  • Record purpose: Is the snapshot supporting physical-content reconstruction, a disposition decision or a particular recordkeeping obligation?

Do not transfer US device obligations to other product categories or device markets. Keep binding regulation separate from audit material, engineering guidance and proposed manufacturing practice. Use audit material to frame audit questions rather than establish current law; exclude historical regulatory citations from the current-law mapping. Assess ISO 13485 readiness against applicable requirements and your intended activities.

NASA’s Systems Engineering Handbook discusses configuration management as an engineering practice concerned with knowing product configuration. That is engineering context here, not a device-manufacturing obligation.

Treat this article’s snapshot model as proposed manufacturing practice. Do not infer a prescribed FDA as-built form, universal component-detail level, sample size or retention interval from it.

04Capture, reconcile, review and preserve the snapshot

A practical lifecycle starts with a defined handoff, not simply a report-generation date. Completion of assembly and completion of configuration-changing rework are useful snapshot points because each gives the next responsible person a bounded physical state to review. The following sequence is a proposed manufacturing control, not a prescribed legal workflow.

  1. Select the unit and cut-off. Identify the physical product, the manufacturing handoff and the time through which configuration events will be included.
  2. Identify the applicable build baseline. Establish which planned component revisions and authorised changes apply to that unit rather than defaulting to the latest plan.
  3. Capture physical events. Record installation, removal and replacement against the unit and component position. Picking, issuing and staging material establish availability or movement, not installation.
  4. Reconcile installed contents. Compare the resulting configuration with the applicable baseline and investigate unmatched components, unexplained absences and unresolved substitutions before presenting the snapshot as reviewed.

The local procedure can specify acceptable installation evidence: for example, an operator-confirmed assembly entry identifying the unit, component and position, with inspection confirmation where appropriate. A scan alone is insufficient unless its transaction meaning establishes installation. Link relevant manufacturing execution records rather than copying the entire execution history into the snapshot.

Useful local states are provisional for an incomplete or unreconciled snapshot; under review when submitted for assessment; reviewed when the designated reviewer has completed the defined configuration checks; and superseded when a successor represents a later or corrected state. These labels describe this proposed workflow, not legally prescribed statuses.

Responsible people assess discrepancies and supporting evidence, recording resolutions or outstanding questions under the applicable quality procedures. Use the distinction in the opening section when interpreting review status. Preserve the reviewed version. For subsequent physical changes or corrections, create a linked successor with its reason and review status rather than silently replacing earlier contents.

From physical events to a reviewed snapshot
  1. 1
    Select the cut-offIdentify the physical unit and reconstruction time.
  2. 2
    Fix the baselineSelect the controlled build definition and applicable changes.
  3. 3
    Capture physical eventsRecord installations, removals and replacements.
  4. 4
    Resolve installed contentDetermine each tracked position's occupant at the cut-off.
  5. 5
    Reconcile differencesCheck identities, authorisations and supporting evidence.
  6. 6
    Record human reviewAssess uncertainty and document the review decision.
  7. 7
    Preserve the versionLink subsequent snapshots without overwriting this state.
A proposed sequence connecting capture, reconciliation and human review.

05Model installed content, authority and supporting evidence

A practical snapshot model separates installed content, change authority and supporting evidence. The fields below are proposed implementation choices for reconstruction and review, not mandated database fields. Keep detailed manufacturing execution records elsewhere and reference only the records needed to explain the physical configuration.

Header and installed-item set

Give the header a snapshot identity, product-unit identity, cut-off time with time zone, controlled baseline reference and explicit snapshot status. Include a predecessor reference and, when applicable, a superseding-snapshot relationship. Keep snapshot review status distinct from product disposition. For document control, reference the specific revision of the relevant configuration specification, rather than a link that always opens the latest version.

For each installed-item entry, record physical position, parent position, part number, part revision, serial or lot identity where applicable, quantity and unit of measure. Distinguish an identity that is not applicable from one that remains unknown. This keeps component traceability gaps visible instead of disguising them as intentionally blank fields.

Keep position identity separate from item identity. In a hypothetical medical-device assembly, a sensor mounting position remains the same position when a replacement sensor becomes its occupant. Parent positions describe containment within the assembly; expand them only far enough to identify relevant installed content. Stop at an identified subassembly when deeper detail is unnecessary for the snapshot’s purpose, rather than building a complete genealogy traversal.

Changes, authority and evidence

Exclude removed components from the current installed-item set. Preserve their removal and replacement events separately, with affected positions and links to earlier snapshots. A reviewer can then explain how the current occupant arrived without treating every previously fitted component as still installed.

Represent substitutions and deviations through references to their authorisation, affected units or positions, and conditions of use. Keep the deviation-management record responsible for the approval rationale and decision history. The snapshot still identifies the actual installed part and revision: an authorisation reference cannot substitute for that identity.

Link configuration-relevant inspection records or verification evidence to both the affected item and snapshot. Record separately the human review conclusion about applicability and sufficiency, including unresolved limitations. A reference establishes where evidence can be found; it does not establish that the evidence covers the installed revision, its installation condition or the configuration after replacement.

Proposed snapshot and evidence relationships

Configuration snapshot

Identifies the unit, cut-off and controlled baseline.

  • snapshot_id
  • product_unit_id
  • as_of_time
  • baseline_ref
  • snapshot_status
  • supersedes_snapshot_id

Installed item

Belongs to a snapshot at a physical position.

  • snapshot_id
  • position_id
  • parent_position_id
  • part_number
  • part_revision
  • component_serial_number
  • component_lot_id
  • quantity
  • unit_of_measure

Configuration event

Records a physical change and its timing.

  • event_id
  • product_unit_id
  • position_id
  • event_type
  • removed_component_ref
  • installed_component_ref
  • effective_at
  • recorded_at
  • authorisation_id
  • source_record_ref

Change authority

Links approval to its scope and conditions.

  • authorisation_id
  • authorisation_type
  • approval_ref
  • scope_ref
  • conditions_ref

Evidence reference

Connects supporting records to affected snapshot content.

  • evidence_id
  • snapshot_id
  • position_id
  • evidence_ref
  • evidence_revision

Snapshot review

Records a human decision about this snapshot.

  • review_id
  • snapshot_id
  • reviewer_id
  • review_decision
  • decision_at
  • unresolved_issue_ref
Installed items connect to physical events, authority, evidence and review.

06Worked case: an authorised bracket substitution

Assume a hypothetical medical-device instrument console named Unit Alder. Its planned mounting bracket is Standard revision A. Alternate revision B is authorised specifically for Unit Alder under the hypothetical reference Alder Substitution Approval. All component quantities use pieces. This example illustrates a proposed recording method, not a legal requirement or a verified device outcome.

The assembler records installation of Alternate revision B at the console’s mounting-bracket position, with its applicable lot identity, Lot Birch. At the post-installation snapshot, the entry preserves the difference between the plan and the physical content:

Snapshot fieldExample entry
Unit and positionUnit Alder; mounting-bracket position
Original planned itemStandard bracket, revision A
Actual installed itemAlternate bracket, revision B
Applicable component lotLot Birch
Authorisation and scopeAlder Substitution Approval; Unit Alder only

The installation evidence reference accompanies this entry, allowing a reviewer to check the recorded part, revision and lot against the installation record. A substitution flag alone would omit the identity needed to reconstruct the console’s contents. The original planned baseline remains identifiable; it is not edited retrospectively to show Alternate as though that had always been the plan.

Authorising this substitution does not, by itself, establish performance equivalence or revise the general product definition. For related decisions, distinguish alternate-material planning in the BOM from broader changes handled through engineering change control.

The human reviewer checks whether Alder Substitution Approval names Unit Alder and Alternate revision B, then evaluates the referenced installation evidence. The resulting review entry identifies that scope and any outstanding question. An approval for another console, another bracket revision or a later manufacturing change would not answer this unit-specific question.

07Worked case: reconstructing a device after rework

Assume Unit Birch is a hypothetical medical-device controller with a serialised display assembly. Its installed display, identified as Display Alder, is removed during authorised rework and replaced by Display Cedar. These names represent distinct component serial identities; quantities are measured in pieces. Assume the rework authority permits Cedar at revision Maple for this unit, subject to the procedure’s acceptance activities.

SequencePhysical content and record treatment
Earlier snapshotDisplay Alder, revision Ash: one piece installed in Unit Birch’s display position.
Removal eventAlder leaves the display position. Record its identity and link the removal to the authorised rework record.
Replacement installationDisplay Cedar, revision Maple: one piece installed in the same position, linked to that rework authority.
Proposed successor snapshotCedar is the installed display. Alder remains traceable through the earlier snapshot and removal event, not through a current installed-content row.

The installed quantity is unchanged between the earlier and successor snapshots: one piece is replaced by one piece. The temporary empty position belongs to the event sequence. Matching quantities therefore do not demonstrate matching configuration; the component identity and part revision have changed.

The proposed snapshot links Cedar to its part identifier, revision Maple, rework authority and configuration-relevant evidence. Evidence collected on Alder stays associated with Alder and the configuration evaluated. It is not relabelled as evidence for Cedar merely because both assemblies occupy the same position.

The responsible reviewer assesses which existing evidence remains applicable and identifies further evaluation under the rework procedure. That assessment considers what the replacement and installation could affect rather than prescribing a universal retest programme. Keep the complete execution history and verification records in their own record; link any applicable rework disposition.

In this example, the reviewer accepts the successor snapshot as an accurate physical-content record but leaves device acceptance pending until the identified evaluation is completed and reviewed.

08Reconcile systems without confusing records with reality

A practical division of responsibility gives controlled product definition ownership of the baseline, material records ownership of issued identities, execution records ownership of installation and removal events, and quality records ownership of authorisations and dispositions. Link these records rather than making every system maintain an independent account of installed content.

Agreement between imports is not confirmation of physical installation: several records may repeat the same issue transaction. Reconciliation evaluates what each event means, which product and position it concerns, and what supports it. An issued component may remain unused; an accepted message establishes receipt of data, not attachment of a part.

Distinguish effective time, when the physical action occurred, from recorded time, when its record entered the system. For a historical cut-off, use effective time to place supported physical events and recorded time to distinguish what was known then from what was learned later. Preserve both views when a delayed offline entry changes the reconstructed snapshot; do not silently rewrite the earlier view.

  • Duplicate messages: use stable source-event references to recognise retransmission without creating another installation.
  • Reversed events: link the reversal to its original event and identify whether it cancels an erroneous record or documents a physical removal.
  • Conflicting identifiers: preserve the conflicting values and resolve their product, component and position references before treating them as equivalent.
  • Changed source revisions: retain the revision used in the snapshot and an explicit correction relationship to its replacement; avoid references that silently resolve to the latest version.

Correcting a factual record is different from authorising a physical product change. Reconstructing what happened does not retrospectively approve the action. Keep the correction rationale and supporting evidence distinct from the quality disposition, with traceable history supporting data integrity.

When the installed state remains indeterminate, preserve that uncertainty rather than selecting the most convenient record. Seek appropriate physical inspection or documentary confirmation, recording its limits. Route the unresolved case through the applicable nonconformance or deviation process for a human decision on further investigation and product disposition.

09Worked case: recovering a late installation record

Assume Unit Cedar is a hypothetical medical-device console still under manufacturer control. An optional handle assembly, quantity one piece, was installed under an authorised instruction before the snapshot cut-off. Its offline installation record arrived after the snapshot had been reviewed. All quantities in this example use pieces.

The preserved snapshot lists no handle assembly. The late record identifies Unit Cedar, the installed handle’s part identity and revision, the installation time, and the instruction authorising installation. The discrepancy is an incomplete historical representation, not a new installation after the cut-off. A missing snapshot entry does not itself establish physical absence.

Apply the effective-time and recorded-time distinction above: the supported installation time places the handle before the cut-off; the later receipt time explains when its record became available. Review the supporting record and related entries in the process event log for conflicting identity or timing information rather than treating receipt time as installation time.

Prepare a corrected successor for the same historical cut-off, adding the handle assembly at one piece. Link it to the earlier snapshot, the late installation event and its supporting record. Preserve the original version and record the correction reason, reviewer and decision in the audit trail.

  • Adequately supported event: the responsible human reviewer accepts the corrected snapshot as the reconstructed historical state.
  • Uncertain timing or identity: the reviewer leaves the discrepancy unresolved, records the uncertainty and requests clarification rather than asserting that the handle belonged in that state.

The correction belongs to the same historical cut-off, so the successor needs both a reconstruction date and the later correction date. A reader comparing versions should see that the handle was added to the recorded representation, not installed again. Keep those dates distinct when passing the corrected snapshot to downstream teams.

10Failure modes that make a plausible snapshot misleading

An internally consistent snapshot can still misrepresent physical content. These practical failure-control pairs target errors that can survive a completeness check because every field appears populated and every reference resolves.

Failure mechanismSuggested control
Baseline drift: an old baseline reference opens today's revision, making a historical assembly appear to contain later design changes.Use revision-specific references. During review, reproduce the historical baseline and its component definitions rather than displaying only the latest definition. Treat a reference that cannot recover its intended revision as unresolved.
Ambiguous identity: a supplier revision is treated as an internal revision because both occupy an undifferentiated revision field.Label identifier types explicitly and maintain supplier-to-internal mappings. Preserve the original supplier part and revision references alongside the internal identifiers; do not overwrite them when assigning an internal identity.
Assumed optional content: an optional position is shown as populated merely because it exists in the product definition.Use distinct states: installed, supported by installation evidence; absent, confirmed unpopulated; not applicable, outside this configuration's scope; and unknown, unresolved. Keep blank fields from silently implying any physical condition.
Quantity confusion: packs are counted as pieces, or material issued, consumed or scrapped is presented as installed content.Record installed quantity with an explicit unit of measure, separately from issued, consumed and scrapped quantities. Where conversion is needed, retain the applicable pack definition and conversion basis rather than assuming that transaction quantities describe installed pieces.

Related reading: recipe versioning for revision-control concepts in production definitions, and net-vs-gross reconciliation for distinguishing quantity bases during material reconciliation.

11Test the model before relying on it

Use this proposed checklist to test whether a reviewer can reconstruct a selected historical unit’s physical configuration from controlled references, without consulting undocumented personal knowledge. Choose pilot cases for their configuration challenges rather than treating a fixed sample size as universally sufficient.

  • Reconstruction: Can the reviewer identify installed content at the chosen cut-off and resolve each supporting reference to its applicable version?
  • Challenge cases: Introduce an ambiguous revision, a removed component, a delayed event, an out-of-scope authorisation and an item whose identity cannot be established. Does each remain visible until addressed?
  • Uncertainty: Does the record distinguish a confirmed empty position from an unknown position, without filling gaps from the planned configuration?
  • Differences: Can the reviewer explain why successive snapshots differ and distinguish physical changes from corrections to recorded information?
  • Accountability: Are source-record correction, configuration review and product disposition assigned to named roles? Can the reviewer identify the human decision and its authority, rather than infer approval from a software status?

Judge the pilot by understandable differences, reproducible cut-offs, resolvable source references and explicit human decisions. Treat unresolved ambiguity as a visible limitation, not a successful reconstruction. Route model revisions through change control; coordinate checks of supporting device manufacturing records with eDHR quality record review. Record remaining limitations and who decides whether the model is suitable for its intended use.

Frequently asked questions

Q.How much internal detail should be recorded for a sealed purchased subassembly?+

For a sealed purchased subassembly, typically record its supplier, part number, applicable revision, lot or serial identity, and installed position. Record internal component identities only where they are controlled, available, and relevant to product risk or later investigation. Do not infer hidden contents from a supplier’s current catalogue. Define the purchased-assembly boundary in the configuration specification, with references to supporting supplier records rather than invented internal detail.

Q.When is a lot-level snapshot useful for devices that are not individually serialised?+

A lot-level snapshot is useful when the identified population shares the same recorded configuration and component allocations support that conclusion. For hypothetical non-serialised medical-device assemblies, this could mean a defined production lot using the same housing revision and seal lot. If a substitution affects only part of that population, establish distinguishable sublots or another controlled grouping rather than describing the entire lot as uniform. A split-batch approach can help preserve that boundary without implying individual-unit traceability.

Q.Should product labels, packaging and supplied accessories appear in the snapshot?+

Include them when they distinguish the supplied product configuration or affect a later configuration decision. Typically, this means the applicable label identity and revision, packaging specification, and accessory identities and quantities—not a duplicate of every packaging operation. State whether the snapshot describes the assembled device or the packaged deliverable; otherwise an absent accessory could mean either incomplete packing or an intentional scope exclusion. Link the applicable instructions for use by controlled identity and revision where they belong to that deliverable.

Q.Should an installed firmware version appear in a physical-product snapshot?+

Yes, when firmware forms part of the manufactured device’s controlled product configuration. Record the installed release identifier against the relevant device or programmable assembly, with a reference to evidence establishing what was loaded. Keep this limited to product identity: network settings, user preferences and infrastructure configuration are outside this snapshot’s purpose. If firmware changes after assembly, preserve the earlier configuration and identify the updated state. Assess compatibility through change control, rather than treating a version entry as proof of acceptable performance.

Q.Does a repeated inspection or test need a new snapshot when nothing physical changes?+

Typically, no new configuration snapshot is needed if the repeated activity leaves every configuration attribute within scope unchanged. Attach the additional inspection record to the existing configuration reference and record the resulting acceptance decision separately. Check what the activity actually involved: opening a sealed assembly and replacing a seal is not an unchanged configuration merely because the same test was repeated. If the repeat exposes an inaccurate snapshot, correct the record with traceable attribution rather than silently replacing its earlier contents.

Q.Can a shared material-kit record establish which components were installed in a particular unit?+

Not by itself. A shared kit establishes what was available or issued, not necessarily what remained installed in each unit. For hypothetical medical-device assemblies drawing from a common kit, use installation allocations or equivalent contemporaneous records to connect component identities to the receiving units. Reconcile unused returns, replacements and scrap before relying on the allocation. Medical device kitting can support this evidence chain, but a kit containing alternative revisions cannot establish a particular unit’s revision without an additional assignment record.

Q.How should a physically installed substitute be represented while its authorisation remains unresolved?+

Record the substitute as actually installed, with its identity, revision, position and installation evidence; do not leave the planned component in place on the record. Show the authorisation status separately as unresolved and reference the pending disposition. A practical control is to hold the affected product while authorised personnel decide whether to accept, rework or reject it. The material review board, where used, supports that human decision. Use the opening distinction when interpreting this unresolved status; retain the assigned decision owner and the information still needed.

Q.What should be handed to service teams without overwriting the manufacturing snapshot?+

Hand over the approved manufacturing snapshot, its product identifier and effective point, relevant configuration-affecting dispositions, and references needed to identify replacement parts. Establish a separate service configuration record that starts from that baseline and records subsequent removals, installations and applicable revisions. Keep manufacturing corrections distinguishable from later service changes: discovering an original recording error is different from replacing a component in the field. Preserve the relationship between both records through an audit trail, so service personnel can distinguish the delivered configuration from the current one.

Primary sources

  • NASA Systems Engineering Handbook Rev 2, engineering practice not medical-device law
  • FDA Quality Management System Regulation (QMSR), current overview

Further reading

  • Medical Device eDHR Software
    Evaluate configured production records and human review through a worked device build.
Talk to us about As-Built Configuration

Want to see how As-Built Configuration could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Where this term comes up
Medical Devices
Related terms
  • → DHR
  • → Configuration Specification
  • → Forward Genealogy Trace
  • → Inspection Record

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC