BAYFORM / STORAGE / PURCHASING GUIDE

Prepare the question
before the decision.

Start by identifying the actual storage object and the subject of its record. Ask whether a reference describes a whole bay, a bin, a tray or a proposed relationship between them. Keep those levels distinct; a shared collection is not evidence of fit. Request the current source for each item and record what its scope covers. Use the register to choose one to three identities, retain independent source issues and arrange the order of a discussion. A layout switch preserves the same records while changing their reading density. When a proposed item or grouping changes, reopen the affected correspondence rather than treating an earlier note as approval. Read location context and document sets before preparing a real request. The local NOT SENT file is a question list, not a storage design or procurement decision.

Read the individual records first.

Every dossier gives its identity, visible appearance direction and the question left unresolved. Keep product identity and evidence applicability separate. A concept image is useful for describing a preference; it cannot establish the actual item, physical sample or current source.

Shelf Bay

Which current source identifies the proposed whole bay and the scope represented by its assembly record?

Parts Bin

Which current container source and counterpart reference belong to this proposed bin question?

Divider Tray

Which current source describes the proposed tray and the subdivision scope under discussion?

Use the field notes for the next step.

Choose the note that matches the relationship under discussion. Do not turn a generic attachment or source note into a complete answer for every record. Retain old sources as history when the proposed issue or context changes, with their relationship to the current proposal visible.

Record hierarchy — A whole object and its related records need separate names.

Container relation — Keep the proposed counterpart beside the bin question.

Location context — A record location is different from a physical placement.

Change history — Preserve the old relationship when the proposal changes.

Quantity language — Count records without implying an order quantity.

Document sets — Make the subject of every file easy to locate.